Non existent domain solution

  • Thread starter Thread starter T0GGLe
  • Start date Start date
T

T0GGLe

Hi,

when performing an nslookup on the one dns server in my domain from a
newly created domain controller I got the "non existent domain" error
and it could not resolve the request.
This was due to the fact that the person who had created that new
domain controller had hard coded (ie typed in)incorrect domain suffixs
in TCP/IP properties. Therefore when the server tried to perform the
nslookup it was being forced to append these incorrect domain suffixs
and therefore could not find the DNS server.
I believe this has led to a load of replication problems and the like
in the domain as AD relies so heavily on DNS working correctly.
Certainly i have plenty of errors in te event logs.

Hope this helps someone as i was pulling my hair out.

Remove the 1 from the email address to contact me.
 
You are going to want to manually fix the problem on servers with static IP
addresses - particularly your domain controllers. Also in your dhcp scope, the option
15 for domain name should be defined instead of manual entries. Depending on your
situation their is a Group Policy that may help. Look under computer
configuration/administrative templates/system - dns client. Be sure to read the full
explanation of what the setting does and it will not apply to domain controllers.

Dcdiag and netdiag are tools that can help you see how bad things are and what needs
fixing and can tell you when things are running right. They are located on the
install disk under the support/tools folder where you will have to run setup. The
links below may help in repairing your problem which may be as simple as using
netdiag /fix and then restarting the netlogon service. --- Steve

http://support.microsoft.com/?kbid=260371
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q294328
 
Back
Top