[366] in athena10
Re: debathena-dns-config status
daemon@ATHENA.MIT.EDU (Greg Hudson)
Mon Aug 4 19:33:41 2008
From: Greg Hudson <ghudson@MIT.EDU>
To: athena10@mit.edu
In-Reply-To: <200808030457.m734vkUi019661@outgoing.mit.edu>
Content-Type: text/plain
Date: Mon, 04 Aug 2008 19:32:54 -0400
Message-Id: <1217892774.12433.103.camel@error-messages.mit.edu>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Hm, this is messier than I had thought.
My plan had been to (1) bring in bind9 and resolvconf, (2) edit
named.conf.options to only listen on 127.0.0.1, and (3) profit. The
bind9 package would take care of configuring a local caching resolver,
and resolvconf would take care of setting up resolv.conf to use it.
Unfortunately, the resolvconf package assumes that some programmatic
source is providing all relevant bits of DNS information. If you're
using DHCP, that's fine, but if you were previously using a static IP
address and a manually configured resolv.conf, the former contents of
your resolv.conf are not consulted. (They are preserved for when the
package is uninstalled, but that's it.) Since bind9 is the only package
providing DNS information, resolv.conf winds up saying just "nameserver
127.0.0.1" and you get no search path.
I am currently thinking that debathena-dns-config should add mit.edu to
the search path (using "echo 'search mit.edu' | resolvconf -a mit" as
suggested by Anders) but that debathena-dns-config should only be part
of the cluster metapackage. I'm afraid of doing too much tampering with
the core network configuration of all -clients machines.
