linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James <james@piku.org.uk>
To: Linux Admin List <linux-admin@vger.kernel.org>
Subject: Re: R: unable to resolve things...
Date: Mon, 13 May 2002 16:21:18 +0100	[thread overview]
Message-ID: <20020513152118.GA6919@piku.org.uk> (raw)
In-Reply-To: <15583.55102.766747.958606@cerise.nosuchdomain.co.uk>

On Mon, May 13, 2002 at 04:09:50PM +0100, Glynn Clements wrote:
| 
| James wrote:
| 
| > | And if you try
| > | nameserver 127.0.0.1 ?
| > 
| > it says:
| > 
| > server:~ # ping www.google.com
| > ping: unknown host: www.google.com
| > 
| > but
| > 
| > server:~ # nslookup www.google.com
| > Server:  mail.rda.lan
| > Address:  10.0.0.5
| > 
| > Non-authoritative answer:
| > Name:    www.google.com
| > Address:  216.239.39.100
| > 
| > works OK. nslookup can find things, but nothing else on that machine
| > can.
| 
| BTW, are you using nscd? That won't have any impact upon nslookup/dig,
| but it will affect anything which uses gethostbyname().

Thankyou! I killed off nscd and it all works now.

God, I thought I was going mad... :)

-- 
There's nothing remarkable about it.  All one has to do is hit the right
 keys at the right time and the instrument plays itself.  -- J.S. Bach  
6AD6 865A BF6E 76BB 1FC2 | www.piku.org.uk/public-key.asc
E4C4 DEEA 7D08 D511 E149 | www.piku.org.uk wnzrf@cvxh.bet.hx (rot13'd)

  reply	other threads:[~2002-05-13 15:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-13 13:41 unable to resolve things James
2002-05-13 13:51 ` R: " David Galligani
     [not found] ` <00e001c1fa84$bec91200$010a910a@es.luxottica.com>
2002-05-13 14:52   ` James
2002-05-13 15:09     ` Glynn Clements
2002-05-13 15:21       ` James [this message]
2002-05-13 15:42 ` rich+ml
2002-05-13 17:13   ` Glynn Clements

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020513152118.GA6919@piku.org.uk \
    --to=james@piku.org.uk \
    --cc=linux-admin@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).