Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!spool.mu.edu!howland.reston.ans.net!newsfeed.internetmci.com!news.mathworks.com!fu-berlin.de!news.belwue.de!news.dfn.de!news.uni-jena.de!news.HRZ.HAB-Weimar.DE!News.HTWM.De!news.tu-chemnitz.de!irz401!uriah.heep!news From: j@uriah.heep.sax.de (J Wunsch) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: SOLVED: Re: [Q] resolv.conf problems Date: 20 Feb 1996 00:24:45 GMT Organization: Private BSD site, Dresden Lines: 23 Message-ID: <4gb4cd$d34@uriah.heep.sax.de> References: <3999600286@f401.n711.z3.ftn> <slrn4i1obe.jnl.hgoldste@bbs.mpcs.com> <slrn4i2830.udp.hgoldste@bbs.mpcs.com> Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) NNTP-Posting-Host: localhost.heep.sax.de Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: knews 0.9.3 hgoldste@bbs.mpcs.com (Howard Goldstein) writes: > The problem seems to stem from the nameserver entry in resolv.conf: .. > When it's present, the resolver functions attempt to find the > non-existent nameserver and the system is toasted from the point where > the bootup console message says "add net defaut:gateway > 204.215.226.90" > > Forunately removing the resolv.conf nameserver entry and running named > in a forwarded/slaved config fixes everything. The more appropriate fix is to use numeric IP addresses for ifconfig and primary route additions. It's becoming a chicken-and-egg problem otherwise. ;) (This is the fix that has been taken in fairly recent systems.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)