[8959] in athena10
Re: [Debathena] #1131: NM/dnsmasq possibly makes
daemon@ATHENA.MIT.EDU (Debathena Trac)
Sat Apr 28 21:59:37 2012
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
From: "Debathena Trac" <debathena@MIT.EDU>
Cc: debathena@MIT.EDU
To: geofft@MIT.EDU, jdreed@MIT.EDU
Date: Sun, 29 Apr 2012 01:59:31 -0000
Reply-To:
Message-ID: <057.f6f8012b970d71bef1e68f22a2cf4caa@mit.edu>
In-Reply-To: <042.0b8b38f9403475473d183cf03aa1665a@mit.edu>
Content-Transfer-Encoding: 8bit
#1131: NM/dnsmasq possibly makes debathena-dns-config obsolete
--------------------+--------------------------------
Reporter: geofft | Owner:
Type: defect | Status: new
Priority: normal | Milestone: Precise Release
Component: -- | Resolution:
Keywords: | Upstream bug:
--------------------+--------------------------------
Comment (by jdreed):
As I understand it (and Greg or Andrew or someone should chime in here),
the primary goals behind a local cacheing nameserver in the first place
was to balance the large number of queries each Athena machine makes
against 10/half networks and DNS servers that were still DECstations
living under someone's desk. I don't think either of those conditions are
true anymore (blah blah older dorm networks blah blah). Should we just
give it up anyway?
I know we briefly discussed this in 2009 when there was that document with
a list of Athena 9 packages and their relevance in a Debathena 10 world,
but I can't find that page right now. Locally installing BIND has been
screwing us since Lucid. Should we just punt it anyway?
--
Ticket URL: <https://athena10.mit.edu/trac/ticket/1131#comment:1>
Debathena <http://debathena.mit.edu>
MIT Debathena Project
