Home » Articles


CodeDigest Navigation

Technology News
No News Feeds available at this time.

Community News
No News Feeds available at this time.
Active Directory Naming information for domain couldn't be found

By Nirmal Sharma
Posted On Apr 20,2008
Article Rating:
Be first to rate
this article.
No of Comments: 5
Category: Directive Service
Print this article.

Active Directory Naming information for domain couldn't be found

Sometimes when you open one of the Active Directory tools you get error message "Naming information couldn't be contacted":

·          Active Directory Users and Computers

·          Active Directory Trusts and Domains

·          Active Directory Sites and Services

·          Domain Security Policy

·          Domain Controller Security Policy

·          Schema Admin

This happens because of the following reasons:

1. SRV records for Active directory domains are not registered in DNS Domain Zone.

2. DNS Server couldn't be contacted for some reason.

3. AA (Host) records for Domain Controller is missing in DNS Zone.

4. NetLogon service on Domain Controller has been stopped.

5. Domain Controller is pointing to a wrong DNS Server.

6. Domain Controller is pointing to a DNS Server which is far away from DC.

7. DNS Server can't be contacted because of network congestions.

8. Heavy use of Domain Controller when DNS Client sends a request to DNS Server to find out domain information.  For example: If an application is running which is using a service account that is sending DNS Query to DNS Server frequently.

Your DNS zone should look like below for SRV Records:

   |-----Forward Lookup Zones
   |             |   _sites
   |             |     |    |
   |             |     |   Default-First-Site-Name
   |             |     |         |
   |             |     |       _tcp--------------- _ldap [SRV]: 0:100:389:
   |             |     |                                  _gc [SRV]: 0:100:3268:
   |             |     |                                  _kerberos [SRV]: 0:100:88:
   |             |     |      
   |             |    _tcp---------------------- _ldap [SRV]: 0:100:389:
   |             |     |                                 _gc [SRV]: 0:100:3268:
   |             |     |                                 _kerberos [SRV]: 0:100:88:
   |             |     |                                 _kpasswd [SRV]: 0:100:464:
   |             |     |        
   |             |    _udp--------------------  _kpasswd [SRV]: 0:100:464:
   |             |     |                                _kerberos [SRV]: 0:100:88:

You must have the above SRVs registerd in DNS zone so that AD Tools can get the list of domain controllers available in domain by executing DcGetDcName API call.

These are the basic guidelines for DNS and TCP/IP Configuration on a server:

1. On DC or DNS server: Make sure DNS server is pointing to server IP address.

2. Make sure Dynamic or Secure Dynamic update is enabled on authoritative Zone.

3. Make sure SOA record in DNS zone is pointing to correct DNS server IP Address.

4. Issue Ipconfig /registerdns from command prompt to register A records of server in zone.

7. If there are two LAN cards make sure Internal NIC of the server is listed first in Binding Order.


Similar Articles

You can contribute to CodeDiget.Com:
Donate to
Article Feedback
Gee whiz, and I thug
Gee whiz, and I thughot this would be hard to find out. [url=]humcqrv[/url] [link=]lzdkflzttc[/link]
This info is the cat
This info is the cat's <a href="">pajaams!</a>
Arcitles like this a
Arcitles like this are an example of quick, helpful answers. [url=]wsydunzras[/url] [link=]zfazhvzfnab[/link]
I will be putting th
I will be putting this <a href="">daznlizg</a> insight to good use in no time.
This makes evytnrhie
This makes evytnrhieg so completely painless.