Re: Numbering nameservers and resolvers
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
On Tue, 17 Aug 2010, Nick Olsen wrote:
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.
Usually network do not loadshare per-packet on BGP, so a TCP session will "always" go to the same dns server, at least for the short duration this TCP session lives. -- Mikael Abrahamsson email: swmike@swm.pp.se
Mikael Abrahamsson <swmike@swm.pp.se> writes:
On Tue, 17 Aug 2010, Nick Olsen wrote:
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.
Usually network do not loadshare per-packet on BGP, so a TCP session will "always" go to the same dns server, at least for the short duration this TCP session lives.
Occasionally I have seen networks (usually small dual-homed ones) that attempt to equally utilize their network pipes by doing per-packet bgp load balancing to both upstreams. Then they wonder why their performance is so irregular. :-) -r
participants (3)
-
Mikael Abrahamsson
-
Nick Olsen
-
Robert E. Seastrom