General discussion



By roman ·
whenever my 2000 server restarts or even when runnig i get so many errors but on only one thing that is "dns failed to connect the error is as follows"registration of DNS record'd245af21-6e88-42d0-9809-96dcf606f._msdcs.baraka.com600 IN CNAME' failed with the following error.

" a connection attempt failed because the connected part did not properly respond after aperiod of time,or estasblished connection failed because connected host has failed to respond.

This conversation is currently closed to new comments.

3 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by CG IT In reply to dns

humm sounds like the alias record [CNAME] is bad. Verify that the information in the CNAME record in DNS is correct.

Collapse -

by BFilmFan In reply to dns

CGIt is as usual correct, but perhaps I can provide some further illumination on this issue.

Active Directory (AD) uses DNS as its locator service to support the various types of services that AD offers, such as Global Catalog (GC), Kerberos, and Lightweight Directory Access Protocol (LDAP). Other non-Microsoft services can be advertised in the DNS, including--but not restricted to--non-Microsoft implementations of LDAP and GC. However, sometimes clients might need to contact a Microsoft-hosted service. For that reason, each domain in DNS has an _msdcs subdomain that hosts only DNS SRV records that are registered by Microsoft-based services. The Netlogon process dynamically creates these records on each domain controller (DC). The _msdcs subdomain also includes the globally unique identifier (GUID) for all domains in the forest and a list of GC servers.

So the question in troubleshooting this issue would be:

Is this the only server in the domain?

Is this the only domain in the AD forest?

Does this server host DNS?

If you could look in the Directory Services, DNS, FRS and System log and give us some further details, we may more easily resolve this issue.

Collapse -

by haileyan In reply to dns

Remove the entry for this server in DNS for Forward Lookup and Reverse Lookup. Then on the server at the command prompt do a ipconfig /registerdns

That should take care of it.

Back to Windows Forum
3 total posts (Page 1 of 1)  

Related Discussions

Related Forums