dcdiag fails - server GUID DNS name could not be resolved

M

Mark

The Exchange 2003 installation pointed me to the dcdiag
utility, which apparently found problems with my DNS
setup. It complains "a6e1e747-5f44-451b-94ed-
26aff4a954e7._msdcs.santaclara.astutonetworks.com's server
GUID DNS name could not be resolved to an IP address" and
to "check the DNS server, DHCP, server name, etc" but
doesn't say what to check for.

DHCP is not running on this machine and when I setup the
DNS, I simply answered a few questions. Since there where
not a lot of questions I expected it not to have a problem.

I've read the Microsoft DNS pages, but can't figure out
what is wrong. I could find no knowledge base article
matching this problem.

The machines name is aruba. When I setup a client to use
it as a DNS server by default nslookup complains that the
domain is non-existant. But when I go into nslookup I can
set to the IP address of aruba and then inquiry about
aruba and get no errors.

[n:\4nt300]nslookup aruba
*** Can't find server name for address 192.168.1.10: Non-
existent domain
Server: dns1-sac.scrmca.sbcglobal.net
Address: 206.13.31.12

*** dns1-sac.scrmca.sbcglobal.net can't find aruba: Non-
existent domain
server 192.168.1.10
Click to expand...
Default Server: [192.168.1.10]
Address: 192.168.1.10
aruba
Click to expand...
Server: [192.168.1.10]
Address: 192.168.1.10


Thanks in advance,
Mark
 
K

Kevin D. Goodknecht

In
Mark said:
The Exchange 2003 installation pointed me to the dcdiag
utility, which apparently found problems with my DNS
setup. It complains "a6e1e747-5f44-451b-94ed-
26aff4a954e7._msdcs.santaclara.astutonetworks.com's server
GUID DNS name could not be resolved to an IP address" and
to "check the DNS server, DHCP, server name, etc" but
doesn't say what to check for.

DHCP is not running on this machine and when I setup the
DNS, I simply answered a few questions. Since there where
not a lot of questions I expected it not to have a problem.

I've read the Microsoft DNS pages, but can't figure out
what is wrong. I could find no knowledge base article
matching this problem.

The machines name is aruba. When I setup a client to use
it as a DNS server by default nslookup complains that the
domain is non-existant. But when I go into nslookup I can
set to the IP address of aruba and then inquiry about
aruba and get no errors.

[n:\4nt300]nslookup aruba
*** Can't find server name for address 192.168.1.10: Non-
existent domain
Server: dns1-sac.scrmca.sbcglobal.net
Address: 206.13.31.12

*** dns1-sac.scrmca.sbcglobal.net can't find aruba: Non-
existent domain
server 192.168.1.10
Click to expand...
Default Server: [192.168.1.10]
Address: 192.168.1.10
aruba
Click to expand...
Server: [192.168.1.10]
Address: 192.168.1.10


Thanks in advance,
Mark
Click to expand...

Remove SBC's DNS from your NIC setup on all machines and point all machines
to the local AD DNS server, preferably should be the DC. The DC should use
its own address for DNS only, unless you have more than one local DNS server
for your AD Domain.

Make sure you have dynamic updates allowed on your forward lookup zone for
your local domain.
 
G

Guest

I changed the DC to only use itself for DNS, but dcdiag
gives the same error.

Problem still not resolved.
 
M

Michael Johnston [MSFT]

Point the server to itself for DNS. Make sure that the DNS zone allows dynamic updates. Stop the netlogon service then open a command prompt. At the
command prompt type "ipconfig /flushdns" and then "ipconfig /registerdns". Start the netlogon service again. In the forward lookup zone for your AD, check in
the _msdcs.santaclara.astutonetworks.com zone for the existance of a cname record by the name a6e1e747-5f44-451b-94ed-26aff4a954e7. It should be there
now. The data portion of this record should show the name of one of you DCs.

Thank you,
Mike Johnston
Microsoft Network Support

--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.
 
G

Guest

Correction - your suggestion did the trick. It just took
a while to show up.

Thanks
-----Original Message-----
In
Mark said:
The Exchange 2003 installation pointed me to the dcdiag
utility, which apparently found problems with my DNS
setup. It complains "a6e1e747-5f44-451b-94ed-
26aff4a954e7._msdcs.santaclara.astutonetworks.com's server
GUID DNS name could not be resolved to an IP address" and
to "check the DNS server, DHCP, server name, etc" but
doesn't say what to check for.

DHCP is not running on this machine and when I setup the
DNS, I simply answered a few questions. Since there where
not a lot of questions I expected it not to have a problem.

I've read the Microsoft DNS pages, but can't figure out
what is wrong. I could find no knowledge base article
matching this problem.

The machines name is aruba. When I setup a client to use
it as a DNS server by default nslookup complains that the
domain is non-existant. But when I go into nslookup I can
set to the IP address of aruba and then inquiry about
aruba and get no errors.

[n:\4nt300]nslookup aruba
*** Can't find server name for address 192.168.1.10: Non-
existent domain
Server: dns1-sac.scrmca.sbcglobal.net
Address: 206.13.31.12

*** dns1-sac.scrmca.sbcglobal.net can't find aruba: Non-
existent domain
server 192.168.1.10
Click to expand...
Default Server: [192.168.1.10]
Address: 192.168.1.10
aruba
Click to expand...
Server: [192.168.1.10]
Address: 192.168.1.10


Thanks in advance,
Mark
Click to expand...

Remove SBC's DNS from your NIC setup on all machines and point all machines
to the local AD DNS server, preferably should be the DC. The DC should use
its own address for DNS only, unless you have more than one local DNS server
for your AD Domain.

Make sure you have dynamic updates allowed on your forward lookup zone for
your local domain.





.
Click to expand...
 
G

Guest

Thanks for the notes on how to clear the DNS cache. It
was working before I got the chance to try it.

-----Original Message-----
Point the server to itself for DNS. Make sure that the
Click to expand...
DNS zone allows dynamic updates. Stop the netlogon
service then open a command prompt. At the
command prompt type "ipconfig /flushdns" and
Click to expand...
then "ipconfig /registerdns". Start the netlogon service
again. In the forward lookup zone for your AD, check in
the _msdcs.santaclara.astutonetworks.com zone for the
Click to expand...
existance of a cname record by the name a6e1e747-5f44-451b-
94ed-26aff4a954e7. It should be there
now. The data portion of this record should show the name of one of you DCs.

Thank you,
Mike Johnston
Microsoft Network Support
Click to expand...
confers no rights. Use of included script samples are
subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all
Click to expand...
responses to this message are best directed to the
newsgroup/thread from which they originated.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

NSLOOKUP and DNS 11
GUID DNS name could not be resolved 3
GUID DNS name could not be resolved 1
GUID DNS name 4
alternate DNS server not querried 1
DNS Server DCDIAG error 8
DCDIAG detects error 3
Reverse DNS not working internally 2

Top