addresses not reslving to name with ping -a

[bjzielinski]

On our remote buildings on the other side of routers, I cannot resolve systems names through ping -a. This is the results I get:

C:\>ping tgillis

Pinging tgillis.midlandco.org [172.18.3.111] with 32 bytes of data:

Reply from 172.18.3.111: bytes=32 time<10ms TTL=126
-------------------
C:\>ping -a 172.18.3.111

Pinging private.ip.address.localhost [172.18.3.111] with 32 bytes of data:

Reply from 172.18.3.111: bytes=32 time=47ms TTL=126
-------------------
I get the same results on that subnet itself as well. This problem just started happening within the last six months, I have no idea what has changed or what is missing.

Bill Zielinski
bzielinski@co.midland.mi.us
County of Midland, Michigan

 

[opediggitty]

It sounds like someone has messes with your reverse mapping of that client or that zone on the DNS servers.

 

[bjzielinski]

I get this result with any host, regardless if they've contacted a DNS server or not.

Bill Zielinski
bzielinski@co.midland.mi.us
County of Midland, Michigan

 

[opediggitty]

How do you know you are not contacting the DNS server when running this command?

 

[bjzielinski]

Well, I don't know if I am contacting DNS, but I know some of the machines in question do not have a DNS server listed, they are involved in other processes that do not require DNS lookups but need to be on the network, so they have not registered with DNS. I guess the main question is where the information 'ping -a' comes from. The machines are NT4, 2k, XP and I think there might be a 98 box in there somewhere, so it doesn't seem to relate to OS.

Bill Zielinski
bzielinski@co.midland.mi.us
County of Midland, Michigan

 

[Yuz]

I get this too, but only when initiating the &quot;ping -a&quot; from XP machines. I believe it started happening after the pc's were updated using window's update. Any help with fixing this would be appreciated.
Thanks!
Steve