Bernd Eckenfels writes:
- host is not using the system resolver but contacting name servers directly.
- You may want to use ping to check it, instead.
That's what exactly what I tried before. Does not work either :-(
--
-- Bruno
Philippe Troin writes:
- The parser for resolv.conf is very stupid.
- Try:
-
-search lifl.fr univ-lille1.fr
-search iut-info.univ-lille1.fr
-nameserver 134.206.10.18
-nameserver 134.206.1.4
-nameserver 134.206.1.15
It does not work either because with this configuration only
Le Sun, Sep 16, 2001 at 02:26:49AM +0200, Bruno BEAUFILS ecrit :
{watney-root-/etc}# host sole
sole.lifl.fr does not exist (Authoritative answer)
{watney-root-/etc}# host sole.iut-info.univ-lille1.fr
sole.iut-info.univ-lille1.frA 134.206.40.114
Did you simply try dig, instead of host
There is something I do not understand about resolving hostnames. It seems the
search primitive of resolv.conf does not work properly in sid, nor in woody.
Let's see some of my configuration files :
resolv.conf
search lifl.fr univ-lille1.fr iut-info.univ-lille1.fr
[moving the discussion to [EMAIL PROTECTED]
Bruno BEAUFILS [EMAIL PROTECTED] writes:
There is something I do not understand about resolving hostnames. It seems the
search primitive of resolv.conf does not work properly in sid, nor in woody.
Let's see some of my configuration files :
5 matches
Mail list logo