Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

dcdiag error with dns

Status
Not open for further replies.

columbiavol

Technical User
Sep 18, 2003
44
0
0
US
I am installing Exchange 2003 and running the dcdiag utility. I have a single forest, ttd.com. This is just a test on a single home server. I have DNS records that point to my server. When I ping the server name (SERVER), it resolves to the correct ip address. However, when I do an NSLOOKUP, it tells me

C:\Documents and Settings\Administrator.SERVER.000>nslookup
*** Can't find server name for address 192.168.2.106: Non-existent domain
*** Default servers are not available
Default Server: UnKnown
Address: 192.168.2.106

Any help on this would be greatly appreciated. This DNS error is preventing the dcdiag from working. Here is the message

Doing initial non skippeable tests

Testing server: Default-First-Site-Name\SERVER
Starting test: Connectivity
SERVER's server GUID DNS name could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(a28928c8-d64c-42c5-8556-306ceaf1e155._msdcs.ttd.com) couldn't be
resolved, the server name (server.ttd.com) resolved to the IP address
(192.168.2.106) and was pingable. Check that the IP address is
registered correctly with the DNS server.
......................... SERVER failed test Connectivity
 
Do you have a reverse lookup zone setup on your DNS server?
 
The resolution was to restart the Netlogon service and to make sure dynamic updates were allowed in DNS.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top