I'm running 2 win2k servers (native AD) and have dns running on both, my problem is that the cached zone has disappeared from DNS, so all dns lookups for the internet have slowed.
Check the view menu. Make sure you're set to advanced. The cache folder should still be there. Test the server for caching by removing its connection to the internet, go to an NT workstation that uses the server's dns as primary, type "ipconfig /flushdns" - then ping something that you know should be in the cache on the server. Look for resolution - not reply. If it resolves to IP, then the cache is up. Jim - Synnex Info Tech
I recomend using nslookup from the command line to test your dns server. using the ping method above does not tell you if your primary or seccondary DNS server answered the request. You can find pretty good info on nslookup in the online help under command refference. If for example you are using DHCP in your network and you are passing two DNS addresses, and your server in question is the first one, and it is not responding, you would see a delay until your client timed out and and tried the next server it uses. this would explain your lag in performance, but you would still see name resolution with a ping.
The cache on the DNS servers will not replicate in the clasic sense. It's function is to improve performance, not availability of resolution. As a server resoloves a querry that it is not master for it will cache the data for that entry for a short time. You don't want that information to stay on your system too long, because when the owner of that Domain makes a change to their DNS entries, you will not see it untill your server expires and deletes the cached entry.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.