I've got a Windows Server domain controller running DNS on a small network.  
DNS keeps failing.  If you look at the forwarders it shows the IP address and 
instead of listing the Server FQDN it says <attempting to resolve> or in some 
cases it gives a simple name like BELINDA.  If you unplug the network cable on 
the back of the server and plug it back in the names immediately resolve and 
BELINDA becomes 208-91-4-4.wintersbroadband.  We're out in the country and my 
link to the internet is flakey.  I suspect I'm losing my internet connection 
and access to the name servers and that the server doesn't reconnect when the 
internet comes back up.  Unplugging the network cable seems to cause DNS to 
repair its connection to the name servers.

Would you agree with my diagnosis?  Is there a fix that would cause DNS to 
automatically repair its connection to the forwarders when the network is 
restored?

Note: Internal connections to the server from other computers on my LAN 
continue to work even though DNS forwarders are down.  So, the server is still 
connected to the LAN - it just appears to be losing its uplink to the internet.

I believe the server is running 2008 R2 although I'd have to go back out there 
to confirm.

Thanks for any help you can provide.

Curt

Reply via email to