Author James Shewey
Recipients James Shewey, Stijn.Hoop, ankitoshniwal, dfranke, loewis, mcjeff, r.david.murray
Date 2017-06-30.17:33:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1498844031.97.0.973800580374.issue5004@psf.upfronthosting.co.za>
In-reply-to
Content
According to the man page for gethostbyaddr "The gethostbyname*() and gethostbyaddr*() functions are obsolete. Applications should use getaddrinfo(3) and getnameinfo(3) instead." - so perhaps using the correct API call might be a good start to resolving this issue, but I found that in my case, I needed to chase the problem upstream instead of downstream. On my Red Hat box, the kernel.hostname value with sysctl was incorrect. I had to re-set it with a  sysctl kernel.hostname=hostname.example.com. This overrides /etc/hosts, so I suspect this is probably not an issue on other distros that do not use sysctl.

The moral of the story being garbage in, garbage out.
History
Date User Action Args
2017-06-30 17:33:52James Sheweysetrecipients: + James Shewey, loewis, r.david.murray, dfranke, mcjeff, ankitoshniwal, Stijn.Hoop
2017-06-30 17:33:51James Sheweysetmessageid: <1498844031.97.0.973800580374.issue5004@psf.upfronthosting.co.za>
2017-06-30 17:33:51James Sheweylinkissue5004 messages
2017-06-30 17:33:51James Sheweycreate