[41194] in North American Network Operators' Group
Re: FIBER CUT: Dallas to West Coast
daemon@ATHENA.MIT.EDU (Eric A. Hall)
Thu Aug 30 22:51:25 2001
Message-ID: <00cd01c131c7$c01180b0$0a0aa8c0@labs.ntrg.com>
From: "Eric A. Hall" <ehall@ehsco.com>
To: <nanog@merit.edu>, "Sean Donelan" <sean@donelan.com>
Date: Thu, 30 Aug 2001 21:50:52 -0500
MIME-Version: 1.0
Content-Type: text/plain;
charset="Windows-1252"
Content-Transfer-Encoding: 7bit
Errors-To: owner-nanog-outgoing@merit.edu
> > DNS in lieu of a routing protocol make me uncomfortable.
> I agree, using DNS in lieu of routing makes me uncomfortable.
> I would rather add a new floor on top, than trying to jack up the foundation
> and change the basement.
The basement is what's leaking. A new roof won't help.
Also, DNS has loads of issues here which make it somewhat unsuitable for this
purpose [1].
Another point, you would be bumping up the DNS cache sizes dramatically.
Ass-u-me a 300 byte response for every query, and it really starts adding up,
especially if you are talking about /24 or heaven forbid /32 entries. You
would almost certainly run out of usable memory on your DNS caches long before
you had solved the original problem.
All told, better to fix the routing system than to lay it on DNS.
[1] http://www.ehsco.com/misc/draft-hall-dns-data-00.txt which has not yet
been submitted pending supplementary statistical research
--
Eric A. Hall http://www.ehsco.com/
Internet Core Protocols http://www.oreilly.com/catalog/coreprot/
