DNS Issues affecting Ping/Nslookup

We are experiencing some issues when attempting to contact an exchange server
from one of our domains. When we ping the server by name it does not append
the DNS suffix for that domain to the host name, however it successfuly pings
the correct IP address. If we ping another exchange server it appends the DNS
Suffix to the host name and again returns the IP address.

Also, when we attempt an nslookup with the just the hostname of the problem
server it fails. If we use nslookup and use the fully qualified domain name
then the nslookup returns the correct IP.

We have checked the A and PTR records in DNS and everything looks correct.
Also have run ipconfig /flushdns and ipconfig /registerdns. Any help would be
appreciated.

Joel <Joel@discussions.microsoft.com> wrote:
> We are experiencing some issues when attempting to contact an
> exchange server from one of our domains. When we ping the server by
> name it does not append the DNS suffix for that domain to the host
> name, however it successfuly pings the correct IP address. If we ping
> another exchange server it appends the DNS Suffix to the host name
> and again returns the IP address.
>
> Also, when we attempt an nslookup with the just the hostname of the
> problem server it fails. If we use nslookup and use the fully
> qualified domain name then the nslookup returns the correct IP.
>
> We have checked the A and PTR records in DNS and everything looks
> correct. Also have run ipconfig /flushdns and ipconfig /registerdns.
> Any help would be appreciated.

Make sure the Exchange server has the correct primary DNS suffix (or
additional DNS suffix, depending on your setup).

Read inline please.

In news:F4707337-9AF4-45C4-ADF9-3747AAE01661@microsoft.com,
Joel <Joel@discussions.microsoft.com> typed:
> We are experiencing some issues when attempting to contact an
> exchange server from one of our domains. When we ping the server by
> name it does not append the DNS suffix for that domain to the host
> name, however it successfuly pings the correct IP address. If we ping
> another exchange server it appends the DNS Suffix to the host name
> and again returns the IP address.
>
> Also, when we attempt an nslookup with the just the hostname of the
> problem server it fails. If we use nslookup and use the fully
> qualified domain name then the nslookup returns the correct IP.
>
> We have checked the A and PTR records in DNS and everything looks
> correct. Also have run ipconfig /flushdns and ipconfig /registerdns.
> Any help would be appreciated.

Use nslookup with the -d2 switch to see exactly what it's doing.

--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps

===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
http://message.wftx.us/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================

Hi,
I have similar problem and I have checked everything mentioned here.

Here is my setup:
2 x DC in one domain
1 x member server
1 DC running DNS server (second has a problem when starting DNS server and I have pointed it to use 2 internal servers)
1 member server is a slave DNS server

I can do nslookup on all servers fine and resolve domains names using just host names and FQDN.

However, I am not able to ping hostnames nor FQDN from the DC that is not running DNS server. I have disabled Netbios over TCP/IP on all servers to make sure it uses DNS.

Because of this situation, my replication does not work as it needs to use FQDN which does not work. I am simply puzzled why nslookup works and ping does not.