[84956] in North American Network Operators' Group
Re: Weird DNS issues for domains
daemon@ATHENA.MIT.EDU (John Dupuy)
Thu Sep 29 13:20:51 2005
Date: Thu, 29 Sep 2005 12:20:17 -0500
To: nanog@nanog.org
From: John Dupuy <jdupuy-list@socket.net>
In-Reply-To: <A310E761-5459-440B-BA92-E160A45550AB@crocker.com>
Errors-To: owner-nanog@merit.edu
If you are talking about strictly http, then you are probably right. If you
are hosting any email, then this isn't the case. A live DNS but dead mail
server will cause your mail to queue up for a later resend on the
originating mail servers. A dead DNS will cause the mail to bounce as
undeliverable. (Oh, and if any of your subs are on mailing lists, they will
be unsubscribed en masse. A nice way to challenge your call center...)
John
At 12:06 PM 9/29/2005, Matthew Crocker wrote:
>>I just tested it from a Verizon DSL host and it worked.
>>
>>You might want to consider reading RFC 2182 though, particularly the
>>part about geographically diverse nameservers.
>
>Yeah, yeah, that is overrated. If my site goes dark and my DNS goes
>down it doesn't really matter as the bandwidth and the web server
>will also be down. Having a live DNS server in another part of the
>country won't help if the access routers handling the traffic for the
>T1 to the school is also down.
>
>Geographically diverse name servers sounds great in theory but for
>this application it won't gain any redundancy.
>
>--
>Matthew S. Crocker
>Vice President
>Crocker Communications, Inc.
>Internet Division
>PO BOX 710
>Greenfield, MA 01302-0710
>http://www.crocker.com
