From owner-freebsd-stable@FreeBSD.ORG Tue Mar 9 18:03:46 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 950A61065678 for ; Tue, 9 Mar 2010 18:03:46 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) by mx1.freebsd.org (Postfix) with ESMTP id 15C9F8FC39 for ; Tue, 9 Mar 2010 18:03:45 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id o29I3hio091743; Wed, 10 Mar 2010 05:03:43 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Wed, 10 Mar 2010 05:03:42 +1100 (EST) From: Ian Smith To: Jeremy Chadwick In-Reply-To: <20100309124609.GA6331@icarus.home.lan> Message-ID: <20100310042709.W85436@sola.nimnet.asn.au> References: <4B9601D9.5030101@bsdforen.de> <20100309210949.F85436@sola.nimnet.asn.au> <20100309124609.GA6331@icarus.home.lan> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-stable@freebsd.org Subject: Re: ntpd does not re-query servers, when a new interface appears 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, 09 Mar 2010 18:03:46 -0000 On Tue, 9 Mar 2010, Jeremy Chadwick wrote: > On Tue, Mar 09, 2010 at 09:27:35PM +1100, Ian Smith wrote: [..] > > Yes, but it looks more like name service that's not operating, ntpd > > seems to be doing its best but can't resolve the hostnames? Right smell, wrong pooch :) Thanks for the pointer to the ntp buglist. > > I've always had to restart named after losing / regaining an interface, > > most noticeably after a suspend/resume (eg a low battery suspend), so I > > run /etc/rc.d/named restart from rc.resume. This looks like a similar > > issue perhaps, though I don't see why restarting only ntpd would fix it. > > named is supposed to auto-probe for interfaces at a specific interval; > see the "interface-interval" option. I forget what the default is, > but on our servers we explicitly disable it by setting it to 0. // We have no dynamic interfaces, so BIND shouldn't need to // poll for interface state {UP|DOWN}. // (will this fix need to reload after suspend/resume?) interface-interval 0; It's rare, maybe twice a year, that this laptop cum server suspends from a 2hr+ lack of power - inverter failures, rewiring etc - so restarting named on resume makes more sense than constant iface polling 'in case'. cheers, Ian