General discussion

Locked

dcdiag shows DNS error ...help

By netforce ·
Although running nslookup shows my ip/server name is resolved, when i run dcdiag /q it gives me this error:

The host cba0839d-5862-40ff-86da-51c72a648a87._msdcs.hq.sf.com could not be resolved to an IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name

(cba0839d-5862-40ff-86da-51c72a648a87._msdcs.hq.sf.com) couldn't be resolved, the server name(server-1.hqsf.com) resolved to the IP address (10.10.0.5) and was pingable. Check that the IP address is registered correctly with the DNS server. ........ SERVER-1 failed test Connectivity


My clients can access server/gateway internet via DHCP OK. Everythings seems ok except for this error in dcdiag concerning my DNS. Yes i have my zones set to enable dynamic updates.

Here's what my servers ipconfig/all reports:

Windows IP Configuration

Host Name . . . . . . . . . . . . : server-1
Primary Dns Suffix . . . . . . . : hqsf.com
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : hqsf.com

Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : hqsf.com
Description . . . . . . . . . . . : 3Com 3C905TX-based Ethernet Adapter (Generic)
Physical Address. . . . . . . . . : 00-60-97-C5-49-47
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.10.0.5
Subnet Mask . . . . . . . . . . . : 255.0.0.0
Default Gateway . . . . . . . . . : 10.10.0.1
DNS Servers . . . . . . . . . . . : 10.10.0.5

Any help appreciated

This conversation is currently closed to new comments.

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

All Comments

Collapse -

DCDIAG Deep Analysis

by BFilmFan In reply to dcdiag shows DNS error .. ...

Try running this command line:

dcdiag /v /e /f:dcdiagLOG.txt /ferr:dcdiagERROR.txt

_MSDCS DNS Zones are DNS records beginning with an underscore are for servers to locate resources, for example _GC, means Global Catalog and _DC means Domain controller. While these resource records exist in Windows 2000, in Windows Server 2003 these _MSDCS records have been moved to their own zone. The benefit of this new arrangement is that you can control the resource replication. For example, you may want to replicate records to all Domain Controllers in the Forest, or perhaps you want to restrict replication to Domain Controllers in the local domain.

The (cba0839d-5862-40ff-86da-51c72a648a87._msdcs.hq.sf.com) is the SID for your DNS server.

You might try running the command on your DNS server:

IPCONFIG /REGISTERDNS just to make sure that it has correctly registed itself.

Is this an Active Directory integrated zone?

Collapse -

by netforce In reply to DCDIAG Deep Analysis

I've ran ipconfig /registerdns already, but still get the same error in dcdiag.

here is the result of :
dcdiag /v /e /f:dcdiagLOG.txt /ferr:dcdiagERROR.txt:


Domain Controller Diagnosis

Performing initial setup:
* Verifying that the local machine server-1, is a DC.
* Connecting to directory service on server server-1.
* Collecting site info.
* Identifying all servers.
* Identifying all NC cross-refs.
* Found 1 DC(s). Testing 1 of them.
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\SERVER-1
Starting test: Connectivity
* Active Directory LDAP Services Check
The host cba0839d-5862-40ff-86da-51c72a648a87._msdcs.hq.sf.com could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name

(cba0839d-5862-40ff-86da-51c72a648a87._msdcs.hq.sf.com) couldn't be

resolved, the server name (server-1.hqsf.com) resolved to the IP

address (10.10.0.5) and was pingable. Check that the IP address is

registered correctly with the DNS server.
......................... SERVER-1 failed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\SERVER-1
Skipping all tests, because server SERVER-1 is
not responding to directory service requests
Test omitted by user request: Topology
Test omitted by user request: CutoffServers
Test omitted by user request: OutboundSecureChannels
Test omitted by user request: VerifyReplicas
Test omitted by user request: VerifyEnterpriseReferences

Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
For the partition (DC=ForestDnsZones,DC=hq,DC=sf,DC=com) we

encountered the following error retrieving the cross-ref's

(CN=d28185ab-9fce-4be8-8214-1265bd04a9fe,CN=Partitions,CN=Configuration,DC=hq,DC=sf,DC=com)

information:
LDAP Error 0x3a (58).
......................... ForestDnsZones failed test CrossRefValidation
Starting test: CheckSDRefDom
For the partition (DC=ForestDnsZones,DC=hq,DC=sf,DC=com) we

encountered the following error retrieving the cross-ref's

(CN=d28185ab-9fce-4be8-8214-1265bd04a9fe,CN=Partitions,CN=Configuration,DC=hq,DC=sf,DC=com)

information:
LDAP Error 0x3a (58).
......................... ForestDnsZones failed test CheckSDRefDom

Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
For the partition (DC=DomainDnsZones,DC=hq,DC=sf,DC=com) we

encountered the following error retrieving the cross-ref's

(CN=dc9b0907-6244-46b9-91b5-d138a558b98b,CN=Partitions,CN=Configuration,DC=hq,DC=sf,DC=com)

information:
LDAP Error 0x3a (58).
......................... DomainDnsZones failed test CrossRefValidation
Starting test: CheckSDRefDom
For the partition (DC=DomainDnsZones,DC=hq,DC=sf,DC=com) we

encountered the following error retrieving the cross-ref's

(CN=dc9b0907-6244-46b9-91b5-d138a558b98b,CN=Partitions,CN=Configuration,DC=hq,DC=sf,DC=com)

information:
LDAP Error 0x3a (58).
......................... DomainDnsZones failed test CheckSDRefDom

Running partition tests on : Schema
Starting test: CrossRefValidation
For the partition (CN=Schema,CN=Configuration,DC=hq,DC=sf,DC=com)

we encountered the following error retrieving the cross-ref's

(CN=Enterprise Schema,CN=Partitions,CN=Configuration,DC=hq,DC=sf,DC=com)

information:
LDAP Error 0x3a (58).
......................... Schema failed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom

Running partition tests on : Configuration
Starting test: CrossRefValidation
For the partition (CN=Configuration,DC=hq,DC=sf,DC=com) we

encountered the following error retrieving the cross-ref's

(CN=Enterprise Configuration,CN=Partitions,CN=Configuration,DC=hq,DC=sf,DC=com)

information:
LDAP Error 0x3a (58).
......................... Configuration failed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom

Running partition tests on : hq
Starting test: CrossRefValidation
For the partition (DC=hq,DC=sf,DC=com) we encountered the following

error retrieving the cross-ref's

(CN=HQSF,CN=Partitions,CN=Configuration,DC=hq,DC=sf,DC=com)

information:
LDAP Error 0x3a (58).
......................... hq failed test CrossRefValidation
Starting test: CheckSDRefDom
......................... hq passed test CheckSDRefDom

Running enterprise tests on : hq.sf.com
Starting test: Intersite
Skipping site Default-First-Site-Name, this site is outside the scope

provided by the command line arguments provided.
......................... hq.sf.com passed test Intersite
Starting test: FsmoCheck
GC Name: \\server-1.hqsf.com
Locator Flags: 0xe00003fd
PDC Name: \\server-1.hqsf.com
Locator Flags: 0xe00003fd
Time Server Name: \\server-1.hqsf.com
Locator Flags: 0xe00003fd
Preferred Time Server Name: \\server-1.hqsf.com
Locator Flags: 0xe00003fd
KDC Name: \\server-1.hqsf.com
Locator Flags: 0xe00003fd
......................... hq.sf.com passed test FsmoCheck


Perhaps you can understand better than I on the above errors.

Thanks

Collapse -

Try this...

by risunantony In reply to

1)Ensure that the DNS settings of the DC/DNS server points to itself in the TCP/IP settings.

2)Delete everything under the _msdcs.x.x.x folder in the DNS management console.

3)Restart the netlogon service.

4)Restart the DNS Server service.

Now, try running the dcdiag again. Check if the error still exists.

Collapse -

by netforce In reply to Try this...

1) is pointing to itself, no problem.

2) ??Thats just it I don't have anything with
the _msdcs.x.x.x folder in the DNS management console.

Here's what i have listed in dns mgmnt:

Server-1
Cached Lookups (folder)
.(root) (subfolder)
Forward Lookup Zones (folder)
hqsf.com (subfolder)
Reverse Lookup Zones (folder)
+0.10.10in-addr.arpa (subfolder)
+0.in-addr.arpa (sub)
+127.in-addr.arpa (sub)
+255.in-addr.arpa (sub)

I feel the need to delete something!!!!

Collapse -

Fixed this problem tonight

by anantau In reply to

I was having the same issue on our server. I was following this line and then did a netdiag /fix

this seems to have resolved my issue. Also, check your soa record and make sure the host is computername.domain.com and the register it.

Collapse -

the fix

by mveira In reply to Fixed this problem tonigh ...

Delete your forward lookup zone, re-create it, then restart the net logon and DNS services.

Collapse -

netdiag /fix worked for me too.

by mynews In reply to Fixed this problem tonigh ...

netdiag /fix worked for me too.
I was having same notifies.

Collapse -

Worked for me

by bilashece In reply to Fixed this problem tonigh ...

Same netdiag /fix worked for me also. You can try with it and will get resolve hopefully.

Collapse -

fixed for me too

by tonyrid2 In reply to Fixed this problem tonigh ...

great tip, it worked for me too!!
thank you

Collapse -

Clearing _msdcs.x.x.x folder

by Get-Smart In reply to Try this...

Clearing the entries under this folder then stopping and starting the DNS and NETLOGON services solved my problem. Thanks!

Back to IT Employment Forum
10 total posts (Page 1 of 1)  

General Discussion Forums