• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 621
  • Last Modified:

Domain Controller DNS Error / netdiag errors


Our monitoring software has detected a DNS error in our active directory enviroment:

Resource - TERRA106
Description - SAAZ monitoring Agent has discovered that the NetDiag DNS test failed with error "No DNS servers have the DNS records for this DC registered". If DNS records are not registered in the DNS server, no other computer or user is able to locate the Domain controller. Please have a Tech work on this immediately.
The Knowledge Base provided below has more information and troubleshooting steps to resolve this particular issue. The troubleshooting steps are provided based on our research and experience.

We are able to ping the servers hostname from other computers on the domain, so DNS for the server is working properly.

We ran DCDIAG which reports no problems, however NETDIAG reports a few problems which appear to be related (attached).

Any suggestions for a solution to this problem would be appreciated.

Thank you

3 Solutions
Henrik JohanssonSystems engineerCommented:
What's the purpose of having multiple NICs enabled?
If not really necessary, disable the one with IP=
Darius GhassemCommented:
Remove the address from the DNS settings and put the actual IP address. Run ipconfig /flushdns, ipconfig /registerdns, and netdiag /fix.

Also, when you have a DC running on a multihomed computer you can see some issues. If you don't need the second nic then disable it if you do make sure you uncheck the register this interface with DNS within the TCP\IP settings.

Also, make sure you have DNS setup to listen on one interface.


Make sure you Binding order is setup correctly.
I saw this as well:
[FATAL] Could not open file C:\WINDOWS\system32\config\netlogon.dns for reading.

Do this :

1. Stop DNS service. (Net Stop DNS)
2. Stop Netlogon Service (Net Stop NEtlogon)
3. Rename the file above file netlogon.dns along with netlogon.dnb (put .OLD after their names to remember easily later on).
4. Start DNS Service (Net Start DNS)
5. Start Netlogon Service (Net Stat Netlogon).

Netlogon Service create Netlogon.dns and Netlogon.dnb files automatically which contain the information of the Zones. Including the GUID and SRV records of the DCs.


Free learning courses: Active Directory Deep Dive

Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.

Darius GhassemCommented:
Usually the Error descriped here is because of using the wrong verison of netdiag [FATAL] Could not open file C:\WINDOWS\system32\config\netlogon.dns for reading.

Make sure you are using the correct verison of netdiag and dcdiag for your server since this will give you false information like the above error.
1. Run below string from  command prompt

net stop dns & net stop dnscache & net stop netlogon & ipconfig/flushdns & ipconfig/registerdns &  net start dns & net start dnscache & net start netlogon & net stop ntfrs & net start ntfrs

2. start -> run -> ncpa.cpl ->  advance menu -> advanced settings
check bind order. Adapter : LAN should be at first
if it still not work then
3. stop dns and netlogon service, go to "system32\config" and rename netlogon.dns and netlogon.dnb to netlogon.dns_ and netlogon.dnb_. and then start both stopped services.
restart windows time service once.
ipconfig/flushdns and ipconfig /registerdns

at last check netdiag /q

server is running 64 bit windows then check file version for netdiag .exe
netdiag 32 bit version = 5.2.3790.3959
netdiag 64 bit version = 5.2.3790.1830

and replace netdiag .exe with  64 bit version
servicadAuthor Commented:
Excellent solutions posted by experts

Featured Post

Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now