From owner-freebsd-questions@FreeBSD.ORG Thu Oct 21 11:44:22 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 936C5106564A for ; Thu, 21 Oct 2010 11:44:22 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms16-1.1blu.de (ms16-1.1blu.de [89.202.0.34]) by mx1.freebsd.org (Postfix) with ESMTP id 2377A8FC16 for ; Thu, 21 Oct 2010 11:44:21 +0000 (UTC) Received: from [193.31.11.193] (helo=current.Sisis.de) by ms16-1.1blu.de with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1P8tZC-0001i6-St; Thu, 21 Oct 2010 13:44:19 +0200 Received: from current.Sisis.de (current [127.0.0.1]) by current.Sisis.de (8.14.3/8.14.3) with ESMTP id o9LBiI3d004102; Thu, 21 Oct 2010 13:44:18 +0200 (CEST) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by current.Sisis.de (8.14.3/8.14.3/Submit) id o9LBiHKF004101; Thu, 21 Oct 2010 13:44:17 +0200 (CEST) (envelope-from guru@unixarea.de) X-Authentication-Warning: current.Sisis.de: guru set sender to guru@unixarea.de using -f Date: Thu, 21 Oct 2010 13:44:17 +0200 From: Matthias Apitz To: Martin McCormick Message-ID: <20101021114417.GA4059@current.Sisis.de> References: <201010211122.o9LBMFa2063759@x.it.okstate.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <201010211122.o9LBMFa2063759@x.it.okstate.edu> X-Operating-System: FreeBSD 8.0-CURRENT (i386) User-Agent: Mutt/1.5.19 (2009-01-05) X-Con-Id: 51246 X-Originating-IP: 193.31.11.193 Cc: freebsd-questions@freebsd.org Subject: Re: How FreeBSD Handles a DNS that is Down X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matthias Apitz List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Oct 2010 11:44:22 -0000 El día Thursday, October 21, 2010 a las 06:22:15AM -0500, Martin McCormick escribió: > This is an extremely novice question on my part, but > after what I recently witnessed, I am not so sure I understand > all I know. > > The normal procedure on internet-connected systems is to > set the resolv.conf file to include at least 2 domain name > servers. Example: > > nameserver 139.78.100.1 > nameserver 139.78.200.1 > > Last night, I had to take down our primary DNS for > maintenance and lots of systems began having trouble of various > kinds. ... The man page of resolv.conf states that the DNS are queried in that order and if one timed out the next is queried; and this is that way for any new resolver request; I've put one which does not exist as first entry (10.0.1.99) and the existing in 2nd place (10.0.1.201) and checked with tcpdump what happened when I do 'ping www.muc.de' three times: # tcpdump -n host 10.0.1.99 or host 10.0.1.201 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on wlan0, link-type EN10MB (Ethernet), capture size 96 bytes 13:37:43.401553 IP 10.49.96.52.44280 > 10.0.1.99.53: 13264+ A? www.muc.de. (28) 13:37:48.403868 IP 10.49.96.52.15468 > 10.0.1.201.53: 13264+ A? www.muc.de. (28) 13:37:48.430125 IP 10.0.1.201.53 > 10.49.96.52.15468: 13264 1/0/0 A 193.149.48.8 (44) 13:37:59.240499 IP 10.49.96.52.42369 > 10.0.1.99.53: 36140+ A? www.muc.de. (28) 13:38:04.242653 IP 10.49.96.52.28001 > 10.0.1.201.53: 36140+ A? www.muc.de. (28) 13:38:04.244321 IP 10.0.1.201.53 > 10.49.96.52.28001: 36140 1/0/0 A 193.149.48.8 (44) 13:38:14.964752 IP 10.49.96.52.24065 > 10.0.1.99.53: 39922+ A? www.muc.de. (28) 13:38:19.967153 IP 10.49.96.52.19756 > 10.0.1.201.53: 39922+ A? www.muc.de. (28) 13:38:19.968822 IP 10.0.1.201.53 > 10.49.96.52.19756: 39922 1/0/0 A 193.149.48.8 (44) This mean that it will at least slow down any new network connection HIH matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/