From owner-freebsd-questions Wed May 2 12: 7:34 2001 Delivered-To: freebsd-questions@freebsd.org Received: from tethys.valhalla.net (tethys.valhalla.net [195.26.32.112]) by hub.freebsd.org (Postfix) with ESMTP id E13DF37B422 for ; Wed, 2 May 2001 12:07:29 -0700 (PDT) (envelope-from mark@tethys.valhalla.net) Received: by tethys.valhalla.net (Postfix, from userid 500) id 3BB1F33008; Wed, 2 May 2001 20:07:29 +0100 (BST) Date: Wed, 2 May 2001 20:07:29 +0100 From: Mark Drayton To: freebsd-questions@freebsd.org Subject: Re: Named resolver trouble Message-ID: <20010502200729.A3273@tethys.valhalla.net> Mail-Followup-To: freebsd-questions@freebsd.org References: <20010502163006.A32702@tethys.valhalla.net> <5.1.0.14.0.20010502103806.026a2110@mail.Go2France.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <5.1.0.14.0.20010502103806.026a2110@mail.Go2France.com>; from LConrad@Go2France.com on Wed, May 02, 2001 at 10:41:37AM +0000 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Len Conrad (LConrad@Go2France.com) wrote: > >from nyx. Does the resolver not query the authoritative server until > >the zone TTL expires? > > When the BIND8 zone master determines that that a zone´s SOA serial > number has changed, it will NOTIFY all NS hosts, and ALSO-NOTIFY > hosts. So can I add an also-notify { ; }; option in named.conf on my authoritative servers to make the resolver update it's cache? The BIND docs suggest NOTIFYs tell slaves that the zone file has changed on the master and that they should update their own. I didn't think a resolving-only nameserver used AXFR to get it's data. I'm still not sure how a resolver deals with changed zone files. For example, say my resolver has been running for a while and has built up a cache of answers including some for example.com. example.com then add a new A record to the example.com. zone like so: an IN A 10.10.10.10 If somebody asks my resolver for the IP of an.example.com. should the resolver: a) determine an.example.com. isn't in it's cache (as example.com just added it) and go off to find it (which I would imagine is correct) or b) wait for the minimum cache time set in example.com's SOA to expire before it goes to look for the record If the first is correct (which seems most plausible) something is broken with my DNS setup as it's not doing that right now. If I ask my resolver for an.example.com it tells me it's non existant. If I ask example.com's NSes they tell me the real answer. Thanks again, -- Mark Drayton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message