This is a discussion on Re: DNS timeout problem - SpamAssassin ; Tony Houghton wrote: > Gary V wrote: > > Tony Houghton wrote: > > > Gary V wrote: > > > > What OS are you running? > > > > > > Linux. Sigh. > > Exactly which distrubution ...
Tony Houghton wrote:
> Gary V wrote:
> > Tony Houghton wrote:
> > > Gary V wrote:
> > > > What OS are you running?
> > >
> > > Linux.
> > Exactly which distrubution and version of that distribution?
> Sorry, Debian unstable amd64.
Setting up a caching nameserver is documented for various operating
systems on the SA wiki page. I also run Debian amd64.
For your Debian machine it is very easy with the following commands.
$ sudo apt-get update
$ sudo apt-get install bind9
The default package configuration is a caching nameserver and the
above commands should be all that is needed to set up and configure it
this way. Check /etc/resolv.conf for nameserver entries and modify or
change the file as needed to say 'nameserver 0.0.0.0' (okay to use
'nameserver 127.0.0.1' with modern software too). See the wiki page
for general information.
I highly recommend the 'resolvconf' package to coordinate the
automated editing of the /etc/resolv.conf file by the various
subsystems such as dhcp, dns, udev scripts, etc.
$ sudo apt-get install resolvconf
The resolvconf scripts run when the interface is brought online.
Since the network will already be online when resolvconf is installed
it won't do anything with /etc/resolv.conf at that moment but will
rewrite that file the next time the networking for an interface is
restarted. Especially for dhcp interfaces this nicely coordinates and
wraps up the configuration so that the nameserver entries are updated
> SA has been slow on it for ages; it's only recently I got fed that
> up with it, mainly due to coming back from a holiday.
It "works for me" on my Debian amd64 machine. (shrug)