?
Solved

Problems resolving DNS while installing exchange.

Posted on 2006-07-24
2
Medium Priority
?
295 Views
Last Modified: 2010-03-19
I'm attempting to install Exchange on a new 2003 server. It's not the DC. One of the steps to set it up is to run a network test. I ran DCdiag on our server andits coming back that it can't resolve the IP. Here's what i'm getting. All windows 2003 servers here, and our DC is also our DNS server.



dcdiag /s:domainserv

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server : Default-First-Site-Name-\domainserver
The host xxxxxxxxxxx-xxxxxx-xxxxxxxxxxc.msdcs.selhs.org could not be resolved to an IP address. Check the DNS server, DHCP, server name etc.
Although the Guid DNS name (xxxxxxxxx-xxxxx-xxxxx.msdcs,sekhs,irg) couldn't be resolved, the server name (domainserv.selhs.org) resolved to the IP address (10.0.0.12) and was pingable. Check that the IP address is registered correctly with the DNS server.

0
Comment
Question by:selhs
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 4

Accepted Solution

by:
jasonduncan76 earned 1000 total points
ID: 17170176
DNS is always so fun,

Are your addresses static or dynamic?

On the dns servers make sure the ips are all internal
Setup the external on the forwarders page.

Check your host records and make sure you can see all your server.

On the exchange box go to %systemroot%\windows\system32\etc\drivers and look for a host file.
If its not there just do a search for host

Edit it with note pad and add your exchange server FQDN...ie mybox.mydomain.com and its internal IP address.
run ipconfig /registerdns.


Good Luck
0
 
LVL 13

Expert Comment

by:Kini pradeep
ID: 17171548
open the dns snap-in and check whether the DC's have registered their alias CNAMES, if not make sure the DC is pointing correctly to the DNS server and stop and start netlogon and it should register the guid, else netdiag /fix should also help.
can you give  a brief idea how the domain is set up and how many are DNS ?
who is pointing to what for dns including the dns server itself.
thanks.
0

Featured Post

Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article will inform Clients about common and important expectations from the freelancers (Experts) who are looking at your Gig.
WARNING:   If you follow the instructions here, you will wipe out your VTP and VLAN configurations.  Make sure you have backed up your switch!!! I recently had some issues with a few low-end Cisco routers (RV325) and I opened a case with Cisco TA…
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.
In this brief tutorial Pawel from AdRem Software explains how you can quickly find out which services are running on your network, or what are the IP addresses of servers responsible for each service. Software used is freeware NetCrunch Tools (https…
Suggested Courses

764 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question