*BSD News Article 46121


Return to BSD News archive

#! rnews 1849 sserve.cc.adfa.oz.au
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!zombie.ncsc.mil!news.mathworks.com!europa.chnt.gtegsc.com!howland.reston.ans.net!Germany.EU.net!zib-berlin.de!news.tu-chemnitz.de!irz401!uriah.heep!not-for-mail
From: j@uriah.heep.sax.de (J Wunsch)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Having problems with DNS
Date: 24 Jun 1995 11:32:56 +0200
Organization: Private FreeBSD site, Dresden.
Lines: 29
Message-ID: <3sgm48$6ff@uriah.heep.sax.de>
References: <3rs2h6$608@news.bu.edu>
NNTP-Posting-Host: uriah.heep.sax.de
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

Mikhail Teterin <mi@cs.bu.edu> wrote:

>/etc/hosts containes 3 dns references (dns and dns1 -- same machine, dns2,
>dns3) I was suggested to create resolve.conf, where I repeat 'nameserver'
>information. I played with /etc/host.conf -- changing 'bind' and 'hosts',
>witrh no success. Any ideas? Thank you!

/etc/hosts does not establish any DNS algorithm.  It's just a fallback
option *instead* of DNS if DNS is not reachable for you.

You're going to use DNS by establishing the file /etc/resolv.conf.
Put your nameserver entries there _numerically_, otherwise you've got
a chicken-and-egg problem.  (The resolver tries to lookup the
nameserver addresses, but since it's using DNS by default, it will
first have to resolve the namserver addresses, but...)

You normally don't need to have an /etc/host.conf, unless you're going
to use the Yellow Plague.  (It's a bad practice to put /etc/hosts in
the lookup order before DNS, since it's containing potentially bogus
data.)

Try finding out where your game's failing by nslookup.

RTFM: nslookup(8), resolver(5).
-- 
cheers, J"org

joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/
Never trust an operating system you don't have sources for. ;-)