While writing a script, I wanted to reference a machine by the computer name that I gave it (e.g. "selenium-rc"). I could not ping it using "selenium-rc", so I tried the following commands to see if the name was recognized.
> traceroute 192.168.235.41 traceroute to 192.168.235.41 (192.168.235.41), 64 hops max, 52 byte packets 1 selenium-rc (192.168.235.41) 0.545 ms 0.241 ms 0.124 ms
Ok, traceroute "found" the name. How? Next ...
> traceroute selenium-rc traceroute: unknown host selenium-rc
Hmm ... the lookup mechanism here must be different because the host is unkown. I'm assuming this is using a system name resolution process whereas the first example was using a process specific to traceroute. Correct?
Then when I came back a bit later ...
> traceroute 192.168.235.41 traceroute to 192.168.235.41 (192.168.235.41), 64 hops max, 52 byte packets 1 minint-q4e8i52.mycorp.net (192.168.235.41) 0.509 ms 0.206 ms 0.136 ms
Ok, different result. The "selenium-rc" name did not change on the machine itself, but the traceroute name resolution process must include some sort of priority and now gives a presumably more authoritative result assigned by another system/service on the network. (Unfortunately, I'm assuming it's a dynamic name that I do not control, and thus it would not be useful in a script.)
Can someone explain the results?