There are 2 parts to DNS. One used most is the name lookup or name to IP address. The other is sometimes call reverse lookup as you pass a IP address and it returns a name. I would look into the DNS setup for the reverse. They are 2 different records in the DNS tables. This can effect many of the networking utilities. ------------------------------------------------- Larry Simonsen Phone: 801-489-2450 Flowserve Corporation Fax: 801-491-1750 PO Box 2200 http://www.Flowserve.com Springville, UT 84663 e-mail: [log in to unmask] ------------------------------------------------- All opinions expressed herein are my own and reflect, in no way, those of my employer. -----Original Message----- From: Chip Dorman [mailto:[log in to unmask]] Sent: Thursday, August 23, 2001 7:21 AM To: [log in to unmask] Subject: PING Curiosity Hi y'all, This is not a big deal, rather a curiosity. We have a pair of "identical" 3ks which are suppose to be configured alike. I have noticed though that to PING, there seems to be a difference between these two machines. By the way they are named Atlantis and Explorer (space shuttles). Anyway, if I ping the addresses with a resolve name option, ping returns its name. However, ping is unable to resolve from address back to name for Explorer. (see below) C:\>ping -a ###.##.1.11 Pinging atlantis.domain.com [###.##.1.11] with 32 bytes of data: Reply from ###.##.1.11: bytes=32 time=50ms TTL=198 Reply from ###.##.1.11: bytes=32 time=50ms TTL=198 Reply from ###.##.1.11: bytes=32 time=40ms TTL=198 Reply from ###.##.1.11: bytes=32 time=50ms TTL=198 C:\>ping -a ###.##.1.12 Pinging ###.##.1.12 with 32 bytes of data: Reply from ###.##.1.12: bytes=32 time=60ms TTL=198 Reply from ###.##.1.12: bytes=32 time=50ms TTL=198 Reply from ###.##.1.12: bytes=32 time=61ms TTL=198 Reply from ###.##.1.12: bytes=32 time=50ms TTL=198 Since we do use DNS here, I now do a ping to each machine using their names. In both cases ping succeeds. C:\>ping atlantis.domain.com Pinging atlantis.domain.com [###.##.1.11] with 32 bytes of data: Reply from ###.##.1.11: bytes=32 time=60ms TTL=198 Reply from ###.##.1.11: bytes=32 time=80ms TTL=198 Reply from ###.##.1.11: bytes=32 time=50ms TTL=198 Reply from ###.##.1.11: bytes=32 time=60ms TTL=198 C:\>ping explorer.domain.com Pinging explorer.domain.com [###.##.1.12] with 32 bytes of data: Reply from ###.##.1.12: bytes=32 time=60ms TTL=198 Reply from ###.##.1.12: bytes=32 time=60ms TTL=198 Reply from ###.##.1.12: bytes=32 time=40ms TTL=198 Reply from ###.##.1.12: bytes=32 time=60ms TTL=198 Explorer was setup several months after Atlantis and seems that there was something missed in its setup. We have compared NMMGR on both machines and they appear the same. Any ideas what we missed? TIA, Chip Dorman Kennametal, Inc. * To join/leave the list, search archives, change list settings, * * etc., please visit http://raven.utc.edu/archives/hp3000-l.html * * To join/leave the list, search archives, change list settings, * * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *