DNS Issue

[bulkmail]

Hi,

We built a new AD and installed DNS. But when I check Event Viewer, I see the following warning:

Event ID 5337
The DNS server for this DC does not support dynamic DNS. Add the DNS records from the file '%systemRoot%\System32\Config\netlogon.dns' to the DNS server serving the domain referenced in that file.

When I looked this up I added the value in the registry but i still see this warning. Also, there are some workstations that cannot join the domain. And of course GPO does not work properly. I am assuming DNS was and is not configured properly.

Anyone have any ideas?

Thanks,

BM

 

[GlenJohnson]

You're not gonna believe this one.

http://search.microsoft.com/search/results.aspx?st=b&qu=Event+ID+5337&view=en-us

Glen A. Johnson
Johnson Computer Consulting
MCP W2K
glen@johnsoncomputers.us


Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884
"Action is the proper fruit of knowledge."
Thomas Fuller (1610-1661); English scholar, preacher

 

[micronmega]

Well for AD to work without errors, you need to be running a dynamic dns setup. From my experience, using your domain controllers as DNS servers works the best. So i would first ask where are your dns servers installed? Are they on your domain controllers? Also are they running an AD integrated zone? Do you have dynamic updates shut off?

By default the netlogon service of a domain controller tries to register itself with DNS ever hour, you can shut this off and register your domain controllers manually but doing that is a pain.

 

[bulkmail]

The only DC is the DNS server. I am not sure what you mean by 'AD intergrated zone'. How can i check to see if DDNS is shut off? Will it be seperate from the regular DNS service?

Thanks,

BM

 

[micronmega]

Well if you open the dns console, and right click on the zone you created, it will tell you what type of zone it is, AD integrated, Standard Primary, or Standard Secondary. Also if you look below that there is a section for Allow Dynamic Updates. Make sure that is ser to yes.

Finally just make sure your DC is pointing to itself for DNS resolution. You can set up forwarding by right clicking on the SERVER in the dns console and going to the forwarders tab.

 

[Troopski]

also, make sure you do not have a .(DOT) zone in you forward lookup zones. if you do, delete it and reboot the server as soon as you get a chance. you will not be able to use forwarding if the server thinks it is a root server.

About the clients, make sure they also have your dnsserver as their primary dnsserver, otherwise you could run into trouble when logging on the domain.

/T