Ping Replies with the root domain instead of the child domain

Hi all

We have windows server 2003 DNS and tree DNS zones in it. Since we have three domains, we created three zones, one for the root domain, and one for each child domain.
The problem that I am having is that I am getting replies from computers in the child domain and showing that they are in the root domain like this:

ComputerName.ChildDomain.RootDomain.com when I ping this computer I get this reply:
ComputerName.RootDomain.com

I went to the DNS and saw that the computer is in the correct zone, then went to AD and saw that the computer is in the correct child domain.

Is this a normal behavior or we have a problem?

Thanks
MedquestAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

MazaraatCommented:
On the PC's what is configured for their primary and secondary DNS server?  They should have only one entry pointing at the child domain dns server.

What IP address are each of the zones listening on....?
NJComputerNetworksCommented:
I would think that this is normal.  What happens when you use NSLOOKUP instead of ping.

http://support.microsoft.com/?kbid=200525
MedquestAuthor Commented:
NSlookup shows that they are in the root domain.

one thing I remembered from Mazaraat comment; is that both DNS server are in the root domain.

will that be the reason?
and if so is there any that we should do to avoid any kind of issues?

Thanks
NJComputerNetworksCommented:
There are many different ways to configure DNS.  There is no right or wrong way to do it...what ever works for your environment is fine.

In your child domains, do you run DNS?  I would assume so.  For example, you might have installed each DC, also as a DNS server.  To check this, look at the TCP/IP settings of you DC's.  Do they point to themselves for DNS?  If they do, they are probably running the DNS server service.  Also, you can check to see if they are running the DNS server service.  In most environments, your DC's will also be the DNS servers.  However, this is not always true.

Remember this basic guideline for TCP/IP settings of your DC and clients:
i.e.

Server Name: ServerDCDNS1
IP: 10.10.10.12
Subnet MAsk: 255.255.255.0
Gateway: 10.10.10.1
DNS: 127.0.0.1 or 10.10.10.12  (Don't point DNS server to ISP DNS servers)
DNS2: <next closest internal Windows DNS server> or <empty>

Client NAme:  Desktop1
IP: 10.10.10.101
Subnet MAsk: 255.255.255.0
Gateway: 10.10.10.1
DNS: 10.10.10.12
DNS2:  <next closest Windows DNS server...never point to ISP DNs servers>

Also, check the DNS suffixes of your clients and servers?  Print these out so we can see them...

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
MedquestAuthor Commented:
I am not sure if that would do it, but we have 12 DCs, and they all point to the two DCs in the root domain even though they have DNS installed and running on all of them.

Thanks a lot
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.