Discussion Locked

Wierd DNS

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I am new to this company. I ran some checks areound the network to get the feel of the place, and in doingso found some oddities. When I run netdiag on the (only one in network) domain controller, it fails the DNS test, saying that the DC is not properly registered. I tried ipconfig /registerdns, but that didint seem to fix the problem. I looked in DNS, but it seemed to me like all the records were there. Any ideas as to whats going on? Clients can log ionto the domain, so the DC is functioning....

6 replies

by lowlands

you can try running netdiag /fix on the DC to get rid of your errors.
Most likely it will not have a big impact since you only have one DC. it might however become a problem once you decide to add some DC's to your environment.

by powlboyjr

I had a similar problem, when I started in my company earlier this year. It seems they had a previous domain controller which had failed and set up a brand new server as a domain controller. If you are running Windows Server 2003, which I assume, go into DNS and make sure both forward and reverse lookup zones are set to Primary Zones. I would also recommend checking the "Store the Zone in Active Directory" check box if the DNS server is a Domain Controller.

by dumphrey

Okay..all dns zones are primary and integrated with AD. But, I dont think any of them are authoritative for the zone. Could that be part of the reason? Also, my certificate service is massivly corrupt, had to uninstall it, and now it wont reinstall, saying I do not have rights to access the container. Could this be related?

by dumphrey

Installed a second dns server and pointed everything at it. Removed old dns and rebuilt it. Now all seems to be good.

This discussion is closed to new replies.