Ping always resolves to a specific ip, but nslookup resolves properly

[Henrik]

On a specific system running Windows 2000 Professional,
running ping on a specific hostname in our network returns
an ip number "199.85.4.55" and reroutes to a web site
pool.com.

When I use nslookup to resolve the hostname, it returns
the correct ip number. Ping always points to the wrong ip
number. I looked into the hosts file and the lmhosts file.

Are there any other files that ping uses to resolve
hostnames?

I would appreciate any assistance. Thank you.

 

[Pegasus \(MVP\)]

Check your hosts file (c:\winnt\system32\drivers\etc\hosts).

 

[William Stacey [MVP]]

Its probably related to dns suffixes. Check the actual domain name that
shows back when you do the ping. What does it say. nslookup works
differently then the local resolver in how and when it appends the dot and
or suffix search list.

 

[Henrik]

The DNS suffix comes back properly.
When I ping pc1, it comes back with pc1.sd.dn.com, but
with the wrong ip number, 199.84.4.55. There are no
entries in the hosts file except localhost 127.0.0.1 and
there is no lmhosts file.
When I use nslookup pc1, it comes back with the right ip
address for pc1.sd.dn.com, 192.168.0.135

Thank you.

 

[Matt Hickman]

The DNS suffix comes back properly.
When I ping pc1, it comes back with pc1.sd.dn.com, but
with the wrong ip number, 199.84.4.55. There are no
entries in the hosts file except localhost 127.0.0.1 and
there is no lmhosts file.
When I use nslookup pc1, it comes back with the right ip
address for pc1.sd.dn.com, 192.168.0.135

DNS resolver always checks local cache first. To eliminate a
corruption of the local cache as the cause, run the command

"ipconfig /flushdns"