Clutch's post before me was spot on... We had the same trouble in our small 15 computer network as the original plaintiff of this thread - slow XP logins to the Windows 2003 Server, computer resource usage spikes, etc. The only exception was on our Win2K machine - no login delay for some reason. However, after implementing the DNS changes on each client computer, including the Win2K, everything improved on the XPs.
I would add that you can Google search on "All Other DNS Domains" and get a step by step for altering the info on the forwarders tab, or try:
http://techrepublic.com.com/5100-6268_11-5112303.html
Cudos to Clutch -
Originally posted by clutch:
Quote:
The Domain Controller should reference itself in its primary DNS entry for its NIC. After doing this, the DC will take a while to boot because it times out on starting the NETLOGON service because DNS hasn't started yet, and it can't register its SRV records. This is normal, and not an issue as it will attempt to start NETLOGON again after DNS is started and will be fine.
All of your clients should have their primary DNS IPs set to that of the DC. At no point on the clients or DC should *ANY* other DNS server IP be listed. You should only have the IPs of AD DNS servers listed to keep resolution working properly. To get outside resolution, add your ISP's DNS server IP to the forwarders tab on the DC for "All Other DNS Domains". This will permit the server to submit recursive queries on behalf of the client to find the addresses of hosts outsided of the hosted DNS zone.
