[128828] in North American Network Operators' Group
Re: Numbering nameservers and resolvers
daemon@ATHENA.MIT.EDU (Nick Olsen)
Tue Aug 17 15:01:32 2010
From: "Nick Olsen" <nick@brevardwireless.com>
To: <nanog@nanog.org>
Date: Tue, 17 Aug 2010 15:00:11 -0400
Reply-To: nick@brevardwireless.com
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
So lets say that you have multiple DNS resolvers in the same ip space that
you advertise from multiple locations. All would be fine for the most part.
But if you had a location equidistant network wise from two POP's wouldn't
it load balance and possibly break some TCP sessions? How would someone get
around this? This is also what OpenDNS does from what I understand.
Nick Olsen
Network Operations
(321) 205-1100 x106
----------------------------------------
From: "Doug Barton" <dougb@dougbarton.us>
Sent: Tuesday, August 17, 2010 2:12 PM
To: "Sven Olaf Kamphuis" <sven@cb3rob.net>
Subject: Re: Numbering nameservers and resolvers
On 08/17/2010 05:11, Sven Olaf Kamphuis wrote:
> tcp/zonetransfer not working reliably is no longer a problem
TCP is a MUST for DNS.
It's used as a fallback in the normal resolution process if an answer
can't fit in a UDP packet for whatever reason. This is true even for
common things like large A record lists, but is only becoming more
frequent in the age of DNSSEC, AAAA, etc. It is unfortunately even more
necessary than we had hoped it would be due to many local network
operators not "getting the memo" regarding EDNS.
hth,
Doug
--
Improve the effectiveness of your Internet presence with
a domain name makeover! http://SupersetSolutions.com/
Computers are useless. They can only give you answers.
-- Pablo Picasso
