On 2015-07-13, at 10:38, Bob Cronin wrote: > Hello all, > PIPE Hostid | Console has begun reporting 192.168.1.64 (which is clearly > nonsense) for one of our mainframes, but when I resolve its hostname > directly, I get its actual IP address, 9.63.66.64, as expected. Why would > Hostid be returning the wrong answer? I suspect some fat fingered > misconfiguration of something, somewhere, but don't know enough about how > this all works to pinpoint the likely cause (so I can go after support to > get it fixed). Any thoughts? > Note that 192.168.1.64 is in the block reserved for private internets, probably assigned by DHCP and not in any configuration file.
-- gil
