CNR 5.5.6 slow to answer queries on intranet when Internet is down - why?

[bread]

Hello,

We're running CNR 5.5.6 on our Intranet inside our firewalls for local address resolution. We've noticed that when our ISP is down, DNS resolutions take longer, approximately 2-3x longer. We understand why this would be the case with a query pertaining to a Internet host, but why would this happen internally when CNR is the authoritative server? We're not sharing the internal info externally, nor with a secondary server. So we're hard pressed to understand the delay. Any insight provided would be appreciated.

Thanks

Brian Read

[jsivulka]

Did you try a power cycle. That works wonders when a slow down is due to system resources not being released properly and when memory leaks occur.

[bread]

The internal DNS servers are rebooted monthly, with the next reboot this Thursday. However, the symptoms only show if the servers cannot access the Internet (fortunately not a common occurance). So I'm wondering if there is some function occurring during the resolution process that I'm not aware of that requires Internet connectivity.

Thanks for your reply.