On Sun, 27 Mar 2005 [EMAIL PROTECTED] wrote: > > Anycast DNS is inadvisable. DNS is specified to work on TCP, and Anycast > > is unsuitable for TCP. > > Your biases against anycast DNS are well known, and don't really add > anything to the discussion at this point.
Biases? Testing of PPLB and facts are not mere "biases". Seems you just want to ignore certain facts. > > Those few who have been promoting the idea of anycast DNS were found to be > > wrong in their assumptions. See previous discussion on the subject in the > > archives. > > Yes, please do see previous discussions. Many of us operate anycast > DNS without problems, and we are aware of the possible problems with > per-packet load-balancing. Yet you don't want to notify others of those problems. Indeed, you object to them being so notified. Strange, I think. Many people run UDP only DNS. UDP only is fine with anycast. I suppose that's OK. But this group is supposed to move people forward. Forward means that people need to be able to use DNS over TCP, and so they should know when they are shooting themselves in the foot so far as the future is concerned. Joe Shen has no compelling need of anycast DNS. It is a bad operational decision to deploy it. And he should get good advice from the DNSOP working group. -- Av8 Internet Prepared to pay a premium for better service? www.av8.net faster, more reliable, better service 617 344 9000 . dnsop resources:_____________________________________________________ web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html
