From owner-freebsd-stable@FreeBSD.ORG Tue Oct 4 15:37:44 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1C36416A41F for ; Tue, 4 Oct 2005 15:37:44 +0000 (GMT) (envelope-from bzag0@yahoo.com) Received: from web53803.mail.yahoo.com (web53803.mail.yahoo.com [206.190.36.198]) by mx1.FreeBSD.org (Postfix) with SMTP id 9FE8243D45 for ; Tue, 4 Oct 2005 15:37:43 +0000 (GMT) (envelope-from bzag0@yahoo.com) Received: (qmail 28941 invoked by uid 60001); 4 Oct 2005 15:37:42 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=uXkLymUJp4jdaxgM4YEiNpSNy2zNMso5JVnpUi+Y3lPeTtniJ/ehh10NdLH1gwKqssbZUpxTN8E/2lgUd6P6LEcwBm5yQyBzxKdswiX5U0vSvzofoUB2uiBamptHx1GJSEsi9dVEm6lB9b+pcr2CnGcGpPpZ5/XMhCoQszsHtNY= ; Message-ID: <20051004153742.28939.qmail@web53803.mail.yahoo.com> Received: from [24.186.205.95] by web53803.mail.yahoo.com via HTTP; Tue, 04 Oct 2005 08:37:42 PDT Date: Tue, 4 Oct 2005 08:37:42 -0700 (PDT) From: Robert Zagarello To: freebsd-stable@freebsd.org In-Reply-To: <200510050050.26723.malcolm.kay@internode.on.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: Re: [freebsd-stable@freebsd.org] Hosts/dns contention in FBSD 5.4 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Oct 2005 15:37:44 -0000 When the DNS can't be reached you need to have the server's host name in your local-LAN accessing client's hosts file. Either way, the client hosts file will be checked first before DNS access (this is true for Windows OSs at least), so because of this you can use any name in your local client, i.e., a NetBIOS name for example (non-dotted up to 15-character, etc.). BZAG ================ --- Malcolm Kay wrote: > I have sytems both at home and at work running > FreeBSD 5.4 > release with a more or less standard installation. > > Both systems are connected to internet routers via a > nics; > and under normal circumstances all works fine -- or > at least > seems to be working fine. In both cases there are > other > computers connected via LAN. > > But if the internet connection breaks -- e.g. the > routers crash > or the ISP connection fails for some reason then > trying to ssh > into the machine from another local machine is a > problem -- > either timing out our taking a very very long time. > > With the internet connection down I notice a similar > problem when > booting in the sendmail script. > > Now it is my understanding that resolution of host > names should > determine from /etc/host.conf and/or > /etc/nsswitch.conf whether > to first try /etc/host or the dns server addressed > by > /etc/resolv.conf > > I believe these should give preference to /etc/hosts > but > never-the-less things get stuck when the dns server > can't be > reached. > > ************/etc/host.conf**************** > # Auto-generated from nsswitch.conf, do not edit > hosts > bind > > ************/etc/nsswitch.conf************ > group: compat > group_compat: nis > hosts: files dns > networks: files > passwd: compat > passwd_compat: nis > shells: files > > Am I missing something? (Probably) > Is this behaviour normal? > Can the lockups be avoided? > > Any help, ideas or clarification would be > appreciated. > > Malcolm Kay > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to > "freebsd-stable-unsubscribe@freebsd.org" >