On Wed, Jun 21, 2000 at 03:28:56PM +0100, Niall O Broin mentioned:
> On Wed, Jun 21, 2000 at 12:05:49PM +0100, John P. Looney (Kate) wrote:
> > Turned out that it was because for some stupid reason, ping tries to do a
> > DNS lookup on the IP it's trying to ping.
> Are you saying that if you try to ping IP address a.b.c.d (rather than
> hostname x.y.z) ping tries to do a reverse DNS lookup of a.b.c.d ? If so,
> that's bizarre, and it certainly isn't happening on this box here i.e. I
> just pinged 192.168.1.103 which can't be resolved (because I took it out of
> my hosts file) and it pinged happily. Just how much did you say you screwed
> with the networking ?
Not that much. I installed a fresh machine to see what was the story -
and the same thing happened.
Just adding the host to the hosts file made it work. The DNS server in
/etc/resolv.conf was way over the network that it couldn't get to - it
wasn't just that the machine it was pinging wasn't DNSable.
--
The words of the unwary are apt to cause needless pain and bloody violence.
- Zen Master Greg
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!
