In working with one customer's system and trying to diagnose what is
possibly a TCP/IP configuration problem, I have received some results I
am not familiar with and I am hoping someone might be able to shed some
light.
I am on system ABC. I do a ping 'ABC'. Normally I would expect ABC to be
named in the ping output, perhaps with its domain name appended.
Instead, I get back a completely different name, XYZ.SOMEDOMAIN.COM.
ping 'ABC'
Verifying connection to host system XYZ.SOMEDOMAIN.COM at address
192.168.2.2.
PING reply 1 from 192.168.2.2 took 0 ms. 256 bytes. TTL 64.
PING reply 2 from 192.168.2.2 took 0 ms. 256 bytes. TTL 64.
PING reply 3 from 192.168.2.2 took 0 ms. 256 bytes. TTL 64.
PING reply 4 from 192.168.2.2 took 0 ms. 256 bytes. TTL 64.
PING reply 5 from 192.168.2.2 took 0 ms. 256 bytes. TTL 64.
Round-trip (in milliseconds) min/avg/max = 0/0/0.
Connection verification statistics: 5 of 5 successful (100 %).
System ABC has three TCP/IP interfaces configured and active on the same
*LIN, one of which is 192.168.2.2.
The local host table contains several entries for 192.168.2.2, including
XYZ.SOMEDOMAIN.COM but *not* ABC.
On the CHGTCPDMN screen (CFGTCP Opt 12), remote DNS servers have been
defined and the search priority is *LOCAL first. The system name is XYZ
and the domain is SOMEDOMAIN.COM.
Does the above output indicate that ABC is being looked up on the DNS
server and found to be 192.168.2.2 but then the local host table is used
to resolve 192.168.2.2 into the name that appears in the ping output,
XYX.SOMEDOMAIN.COM?
FYI, another unusual thing on this system is that they have XYZ defined
in the host table (without any domain name) at address 199.99.99.2, i.e.
XYZ and XYZ.SOMEDOMAIN.COM are two different systems.
Any insight on this would be appreciated.
Thanks,
-Marty
midrange.com
