Re: should resolver read /etc/hosts?

To: Jules Bean <jmlb2@hermes.cam.ac.uk>
Cc: debian-devel@lists.debian.org
Subject: Re: should resolver read /etc/hosts?
From: Joop Stakenborg <aba@casema.net>
Date: Fri, 7 Jan 2000 12:30:47 +0100
Message-id: <[🔎] 20000107123047.A425@aba.dhis.net>
In-reply-to: <[🔎] Pine.SOL.4.10a.10001071120400.16001-100000@red.csi.cam.ac.uk>; from jmlb2@hermes.cam.ac.uk on Fri, Jan 07, 2000 at 11:21:11AM +0000
References: <[🔎] 20000107113238.A23568@aba.dhis.net> <[🔎] Pine.SOL.4.10a.10001071120400.16001-100000@red.csi.cam.ac.uk>

On Fri, Jan 07, 2000 at 11:21:11AM +0000, Jules Bean wrote:
> 
> Yup.  nslookup is the exception, which always uses DNS - that's its job.
> 
> Try 'ping', which will use the system resolver.
> 
> Jules

That's it

Thanks!

BTW, I notice /etc/hosts is -rw------- on my potato system

Joop
-- 

 Joop Stakenborg PA4TU, ex-PA3ABA 
      <pa3aba@debian.org>
 Linux Amateur Radio Software Database
    http://radio.linux.org.au

Reply to:

Follow-Ups:
- Re: should resolver read /etc/hosts?
  - From: Wichert Akkerman <wichert@cistron.nl>

References:
- should resolver read /etc/hosts?
  - From: Joop Stakenborg <aba@casema.net>
- Re: should resolver read /etc/hosts?
  - From: Jules Bean <jmlb2@hermes.cam.ac.uk>

Prev by Date: Re: should resolver read /etc/hosts?
Next by Date: Re: Debian Logo
Previous by thread: Re: should resolver read /etc/hosts?
Next by thread: Re: should resolver read /etc/hosts?
Index(es):
- Date
- Thread