Small network. One MS Active Directory server and 20 or fewer workstations. We were relying solely on the Windows 2000 server (AD) for DNS, DHCP as well as handling many other tasks. I don't like having all the eggs in one basket, so as a first step, I took one of our older machines - still a PIII 450mHz with 576 RAM - and put Debian Woody on it. The idea is for it to take over the DHCP and share the DNS load. DHCP is going no problems. DNS is BIND 9 and is integrated with AD. Regular updates are happening and the logs look good. All necessary zones exist. Shouldn't be a problem - but there is. While internal addresses are responding faster than ever, external addresses are taking longer. Sometimes even Google times-out. If you try to re-load, you usually get the site in your browser - sometimes it takes a couple of attempts. Once you have resolved a root domain (www.google.com
), all other pages in that domain respond very quickly (for example: http://www.google.com/froogle?hl=en&tab=gf&q=
Caching seems to be an issue because 5 minutes later, Google.com will time-out again. All pings inside the network are good but I do get time-outs from both nslookup and dig when testing with some external domains. (dig www.yahoo.com
). Dig will usually respond on the 2nd try and nslookup can take up to 4 or 5 attempts. My db.root file seems fine. Not sure what is happening here... I do still consider myself a Linux noob so your patience and any suggestions are appreciated.