Date: Wed, 2 Aug 2006 08:12:44 -0400 From: Bill Moran <wmoran@collaborativefusion.com> To: "Mark Powell" <M.S.Powell@salford.ac.uk> Cc: freebsd-questions@freebsd.org Subject: Re: Using dnscache locally with FBSD 6.x Message-ID: <20060802081244.32894939.wmoran@collaborativefusion.com> In-Reply-To: <20060802094019.O16501@rust.salford.ac.uk> References: <20060801133245.B9668@rust.salford.ac.uk> <20060801085450.56eadfe5.wmoran@collaborativefusion.com> <20060802094019.O16501@rust.salford.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
In response to "Mark Powell" <M.S.Powell@salford.ac.uk>: > On Tue, 1 Aug 2006, Bill Moran wrote: > > >> However, I use svscan to start up dnscache, and that starts very late in > >> the boot. That means I can't just have the single "nameserver 127.0.0.1" > >> line in resolv.conf, as every lookup would timeout until dnscache started. > >> That means I need to replace resolv.conf early in the boot with the > >> addresses of remote dns caches: > > > > Have you investigated the possibility of moving svscan's startup earlier in > > the boot sequence? I don't know whether the svscan startup script is rcng > > compliant yet, but if it is, you could move it to /etc/rc.d and move it > > _way_ up in the startup sequence. > > I think it is rcng compliant. However, once in /etc/rc.d, how is the order > of execution determined? I expect I will need to get it to run about the > same time that named is usually started. Have a look at the man page for rcorder. IIRC, that covers it pretty well. > > Another option is to put addresses that need to resolve before svscan has > > started into /etc/hosts so that they don't need DNS. This could be > > a maintenance nightmare, though, if there are many addresses. > > That sounds like a nightmare :( > Cheers. It was a thought. -- Bill Moran Collaborative Fusion Inc.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060802081244.32894939.wmoran>