secondary DNS behavious when cutoff from primary DNS
Posted on 2013-01-04
One of my clients manages a central HQ, plus remote sites.
The HQ has a Windows 2008 acting as the primary DNS server,
while the Windows 2008 stand alone servers at the remote sites
all act as secondary DNS servers to the primary.
The forwarding server of these secondary DNS servers is
set to the primary server, and not to the local ISP's DNS
- which to me seems wrong.
The remote site servers also run an in-house web app
When the remote site's Internet link goes down, the local
workstations continue to access the local web app unhindered.
Twenty four hours later, however, the workstations can't
access the web app anymore. The server hasn't been rebooted;
I'm not sure whether the workstation has been switched off
overnight, although I suppose it has.
The two solutions used up till now were connecting to the app
using the local server's IP address, or by inserting the local
server's FQDN and IP pair into the workstation's host file.
Obviously this type of situation doesn't happen too frequently.
What I'd like to know, the next time this happens, is what address
does the web app resolve to on the workstations when it fails ?
Any ideas ?
I'll add the responses asap to the two queries I formulated here
while writing my question.