[80016] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Slashdot: Providers Ignoring DNS TTL?

daemon@ATHENA.MIT.EDU (Patrick W. Gilmore)
Wed Apr 20 15:48:15 2005

In-Reply-To: <Pine.LNX.4.44.0504201520450.4574-100000@localhost.localdomain>
Cc: "Patrick W. Gilmore" <patrick@ianai.net>
From: "Patrick W. Gilmore" <patrick@ianai.net>
Date: Wed, 20 Apr 2005 15:47:46 -0400
To: nanog@merit.edu
Errors-To: owner-nanog@merit.edu


On Apr 20, 2005, at 3:29 PM, Dean Anderson wrote:

>> Or don't.  No one here cares if you do.  Reality trumps lab tests.
>
> "Reality" for the last ten years has been that no one did either  
> PPLB or
> TCP DNS. That reality is changing. It'll probably start to change  
> faster,
> sooner. Then, users will start to notice the problems.

People have been using TCP applications on anycast for at least a  
decade, as I mentioned before.  Since DNS responses tend to be very  
short lived TCP session, it seems to me that if it works for other  
applications (e.g. HTTP), it should work for DNS.

Either way, reality still trumps lab tests, or mailing lists posts.   
Since it has worked, and continues to work, in _THE REAL WORLD_ for  
TCP applications much longer lived than DNS, I suggest that your  
assertion that "users will start to notice the problems" is  
incorrect.  Of course, time will tell which of us is correct.

Maybe I'm insane.  Or maybe you are.   Although I think time has  
already told which of us is....

-- 
TTFN,
patrick

home help back first fref pref prev next nref lref last post