Routing to .US TLD servers
If you (or your customers) have difficulties resolving domains in the US zone, it was moved recently moved to a new set of servers. Nothing special, except they are all in 209 net space, and are being announced as /24 network routes. There is no covering CIDR aggregate being announced, so providers which still filter 209 CIDR blocks (i.e. an obsolete copy of access-list 112) you may have difficulty reaching the new servers. a.gtld.biz. 209.173.53.162 b.gtld.biz. 209.173.57.162 c.gtld.biz. 209.173.60.65 route-server>show ip bgp 209.173.48.0/20 longer BGP table version is 502125, local router ID is 134.24.38.246 Status codes: s suppressed, d damped, h history, * valid, > best, i - internal Origin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path *> 209.173.53.0 134.24.127.30 35 0 1740 7018 701 7786 i *> 209.173.57.0 134.24.127.30 35 0 1740 7018 7786 i *> 209.173.58.0 134.24.127.30 35 0 1740 7018 1 7473 9911 7786 ? *> 209.173.60.0 134.24.127.30 35 0 1740 7018 209 7786 i This is strictly a network routing issue, and has nothing to do the merits of Neustar, ICANN or any other DNS issue. If you, and all your upstreams, accept /24's you shouldn't see any problems.
participants (1)
-
Sean Donelan