Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have three forward lookup zones in my DNS server. When I try pinging a server that's part of lookup zone A from a computer that's part of that same zone, I get a response. If I try pinging a server that's not in the same zone as the computer I'm pinging from, I get nothing. When I try an nslookup of the servers that are not part of the same lookup zone, the names resolve correctly. If I append the domain onto the name, I can ping it just fine.

Is there a way I can fix this? or do I need to keep appending the domain onto the name if the computer I'm trying to ping is not of the same domain as me?

share|improve this question
up vote 3 down vote accepted

You need to append the other domains in your TCP/IP properties if you wish to reach them without the FQDN.

share|improve this answer
I did that too, still no dice – blsub6 Jan 5 '11 at 21:42

Try flushing the DNS cache and then running a network capture on the client and then run ping and nslookup. You should see the DNS queries from the client and the answers from the server, which should give you some idea to what's happening.

share|improve this answer
I've done what B. Riley said above and put those three domains in to the TCP/IP properties. When I do that, I see the DNS queries go out for server.domainA, server.domainB and server.domainC and it answers the third one with an A record. I still can't ping anything that is outside of my parent domain without using the FQDN – blsub6 Jan 5 '11 at 22:45
I see NBNS queries when I try to do a ping, but no DNS queries – blsub6 Jan 5 '11 at 22:52

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.