Date: Sun, 25 Jan 2009 12:42:17 +1100 From: Mark Andrews <Mark_Andrews@isc.org> To: Doug Barton <dougb@FreeBSD.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: <200901250142.n0P1gHv9060982@drugs.dv.isc.org> In-Reply-To: Your message of "Sat, 24 Jan 2009 17:19:40 -0800." <497BBE2C.5060103@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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. > Doug > This .signature sanitized for your protection -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews@isc.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200901250142.n0P1gHv9060982>