Date: Tue, 31 Mar 2009 10:25:22 +0200 From: Mel Flynn <mel.flynn+fbsd.current@mailing.thruhere.net> To: freebsd-current@freebsd.org Cc: Doug Barton <dougb@freebsd.org> Subject: Re: New rc.d/named features for testing: auto-forwarding and wait on boot Message-ID: <200903311025.22219.mel.flynn%2Bfbsd.current@mailing.thruhere.net> In-Reply-To: <49D1B57F.8050903@FreeBSD.org> References: <49D1B261.6010406@FreeBSD.org> <49D1B57F.8050903@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Doug, On Tuesday 31 March 2009 08:17:35 Doug Barton wrote: > > In addition to enabling auto_forward you can also enable > > auto_forward_only which changes from the default 'forward first' to > > (you guessed it) 'forward only'. > And of course, the patch: > http://dougbarton.us/Downloads/rcd-named.diff Snippet: + if [ -z "$firstns" ]; then + if [ ! "$nsip" = '127.0.0.1' ]; then + echo 'nameserver 127.0.0.1' + echo " ${nsip};" >> /var/run/auto_forward.conf + fi I think the hardcoded 127.0.0.1 should be configurable especially considering prepend-domain-nameservers option for dhclient.conf(5). Now you risk using yourself as forwarder if you expose the resolver to the internal network (whether it be through dhclient or statically). Also, maybe the combo of autoforward and dhclient should be guarded against, since there's no telling which comes up first and both dhclient and /etc/rc.d/named might be writing /etc/resolv.conf at the same time / after eachother. Lastly, 127.0.0.1 and ::1 aren't equal, yet they are the same thing ;) -- Mel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200903311025.22219.mel.flynn%2Bfbsd.current>