on 3/15/09 11:08 PM, Robert Hajime Lanning said: > heh, you didn't even get what I was talking about. So, does those > millions of people MANAGE the DNS anycast networks, or even know they > exist? I wasn't talking about any affected community. I was talking > about how many sysadmins manage an anycast network.
I did get what you were talking about, and you were obviously missing the point. The problem with anycast and DNS has absolutely nothing to do with the people who are administering it, since the anycast addresses are just used to serve the DNS queries, and all real administration is done directly to the real IP address of the machine. The anycast address is just an alias that isn't used for anything but DNS. Therefore, route flaps aren't a problem for the administrative side of the house. If you don't get it, then read that sentence again. Route flaps are *ONLY* a problem for the customer side, because they're the only ones who would be doing TCP-based DNS communications to the anycast alias, when their connection gets hosed as a result of a route flap. A flap that messes up routing for the anycast address would have no effect on the route for the real IP address of any given machine, unless that was a problem that affect the whole site and in that case they've got bigger problems to worry about. The admins most likely would never even know if a route flap did occur and did take down some customer communications, if they weren't actively monitoring their systems from the outside and posing as customers. -- Brad Knowles <[email protected]> If you like Jazz/R&B guitar, check out LinkedIn Profile: my friend bigsbytracks on YouTube at <http://tinyurl.com/y8kpxu> http://preview.tinyurl.com/bigsbytracks _______________________________________________ Tech mailing list [email protected] http://lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
