Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 2 subscribers
  • Views 684 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

DNS proxy not correctly resolving local domain

BarryG
I had to power off Astaro for a few hours today, and when it came back up, it got a new IP from the ISP, and (eventually) updated dyndns.org:

(boot)
system.log:2009:05:17-14:53:59 me ddclient[4119]: FAILED:   updating me.dyndns.org: Could not connect to members.dyndns.org.
system.log:2009:05:17-14:59:00 me ddclient[4119]: SUCCESS:  updating me.dyndns.org: good: IP address set to 173.55.5.120

However, the DNS server on Astaro is not correctly resolving my domain name; it's resolving it to the old IP address, even after almost 4 hours since boot.

I checked my upstream resolvers (OpenDNS), and they correctly resolve my domain but Astaro still does not.

Also, I don't see any way to restart the DNS proxy through webmin anymore... in v6, there was an enable/disable button that reset it.

I'm sure it will eventually update, but 4 hours seems excessive.

Thanks,
Barry


This thread was automatically locked due to age.
Parents
  • 0
    Should I open a support case?

    Thanks,
    Barry
  • 0 in reply to BarryG
    Krycek offered the following "button" to flush your DNS: 

    /var/mdw/scripts/named restart


    In the succeeding post, Angelo says that there will be an actual button in V7.5.

    Cheers - Bob
  • 0 in reply to BAlfson
    OK thanks.

    I think I had tried looking in /etc/rc.d/ unsuccessfully.

    Regardless, doesn't it seem that it's a bug if ddclient updates DynDNS on boot but named doesn't get the change?

    Thanks,
    Barry
  • 0 in reply to BarryG
    I know you love the console barry but for regular folks till the button comes up in 7.5, the procedure is simple. If you make any changes to the dns configuration, it reloads and restarts the proxy. So sometimes I just delete my forwarder and add it right back and it restarts dns proxy.[;)] By default named keeps the cache in memory. Its wierd that it didn't refresh for 4 hours though since ttl is fairly low on dyndns servers.
    Ofcourse unless its a core service like webadmin which is in /etc/init.d, everything is controled by middleware so /var/mdw/scripts as I am sure you are aware.
  • 0 in reply to Billybob
    Hi BillyBob, I actually made several changes includinging the allowed networks without success. I didn't try changing the forwarders.

    Thanks,
    Barry
Reply Children
No Data