Return to BSD News archive
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!nntp.gmd.de!nntp.darmstadt.gmd.de!news.th-darmstadt.de!fauern!news.tu-chemnitz.de!irz401!uriah.heep!bonnie.heep!not-for-mail
From: j@bonnie.heep.sax.de (J Wunsch)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: DNS problems with 2.0.5-R
Date: 5 Jul 1995 09:36:16 +0200
Organization: Private U**x site, Dresden.
Lines: 37
Message-ID: <3tdfdg$e8f@bonnie.tcd-dresden.de>
References: <DB6JAK.DnA@crash.cts.com>
Reply-To: joerg_wunsch@uriah.heep.sax.de
NNTP-Posting-Host: 192.109.108.139
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Dave Smith <dsmith@crash.cts.com> wrote:
>... The DNS server (which is now FreeBSD) will
>time out and be unable to find an address. Then just
>a few minutes later without changing anything it will be able
>to find the same address. Here is a typical nslookup session:
(Without the named setup files, there's not much help.)
>> nic.cerf.net
>Server: dns.n2.net
>Address: 204.250.22.10
>
>*** dns.n2.net can't find nic.cerf.net: Server failed
>[wait a few minutes]
>> nic.cerf.net
>Server: dns.n2.net
>Address: 204.250.22.10
>
>Non-authoritative answer:
>Name: nic.cerf.net
>Address: 192.102.249.3
>
>If the second time it found it in the cache, why couldn't it
>find it the first time?
DNS uses UDP queries, they are connectionless. The answer to your
first query eventually arrived after a rather long time, so your
nslookup timed out already. Anyway, the named itself still caught the
answer and kept it in the cache then, so it could immediately answer
it at the second request.
--
cheers, J"org private: joerg_wunsch@uriah.heep.sax.de
http://www.sax.de/~joerg/
Never trust an operating system you don't have sources for. ;-)