Date: Sat, 24 Jan 2009 17:46:22 -0800 From: Doug Barton <dougb@FreeBSD.org> To: Mark Andrews <Mark_Andrews@isc.org> Cc: lev@FreeBSD.org, FreeBSD Stable <freebsd-stable@FreeBSD.org> Subject: Re: BIND 9.4.3-P1: internal_send: 199.7.83.42#53: Device not configured, where 199.7.83.42 is RANDOM IP address Message-ID: <497BC46E.8020209@FreeBSD.org> In-Reply-To: <200901250142.n0P1gHv9060982@drugs.dv.isc.org> References: <200901250142.n0P1gHv9060982@drugs.dv.isc.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Mark Andrews wrote: > In message <497BBE2C.5060103@FreeBSD.org>, Doug Barton writes: >> Mark Andrews wrote: >>> In message <497B9FF4.30605@FreeBSD.org>, Doug Barton writes: >>>> Any time you are using NFS you should maintain the addresses of the >>>> critical hosts in /etc/hosts. Yes, I realize that's anachronistic >>>> (especially for a DNS guy) but it works. Obviously you should make >>>> sure to update them as needed. >>> Or keep a local copy of the zone which contains them. >> I actually considered suggesting that option, but it's unclear to me >> whether or not named would answer at all, even for a local zone, given >> the situation described. > > named will always answer for local zones. > > b.t.w. BIND 9 primes when it attempts to recurse for the > first time. Interesting, thanks! Doug -- This .signature sanitized for your protection
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?497BC46E.8020209>