ChangeIP.com

[johnhenryshammer]

Howdy folks.
I'm pretty new to configuring DNS server, and I cannot solve this problem in spite of trying for hours. No doubt a DNS expert will spot it right away.
Can anyone offer advice?
I recently added a W2K3 R2 server to our W2K domain, which was adprep'd to update th schema. I configured DHCP and WINS on this W2K3 R2 server, no problems there.
We have three AD Integrated DNS servers, all W2K, and one standard secondary W2K DNS server, which gets it;s updates from one of the ADI DNS servers.
I installed DNS on the new W2K3 R2 server, making it AD Integrated.
Won't work. At all. DNS is running, but it won't resolve anything. It has a clear connection to the internet and I can happily browse the web on the server.
I checked the DNS event log and saw events 407 and 408, suggesting a problem with port 53. I ran Port Query which said port 53 was in 'Listening' mode, which I assume is correct.
I checked the dependencies that DNS server relies on, they are all enabled and running.
I run nslookup on the w2K3 , it defaults to the standard secondary DNS server which serves the doamin and resolves ok. I then point nslookup to the W2K3 DNS server, suddenly it can't resolve.
I uninstalled DNS, then re-installed as a standard secondary, still no joy, even with correct dns file.
Reinstalled again as ADI, still no joy.
It's prob something really simple and obvious but I can't see it.

Can anyone offer any assistance?

Thanks if you can.

[danm]

I haven't done a lot of work with DNS on Windows, but there's a few things to try. First, do a "netstat -an" and see if it's listening on port 53 TCP and UDP on your network IP address or on 0.0.0.0. Next, try to do a zone transfer. If you have dig, use "dig <domain> @<dns_server> axfr." If you don't, at least try to look up the SOA with nslookup. Check what records you're getting back to verify it's the correct domain.

Also, make sure you don't have a firewall or antivirus program that's blocking port 53!

Dan