[169639] in North American Network Operators' Group
Re: DNS Resolving issues. So for related just to Cox. But could be
daemon@ATHENA.MIT.EDU (bmanning@vacation.karoshi.com)
Fri Mar 7 05:05:07 2014
Date: Fri, 7 Mar 2014 02:04:09 -0800
From: bmanning@vacation.karoshi.com
To: Rob Seastrom <rs@seastrom.com>
In-Reply-To: <86k3c7cw5w.fsf@valhalla.seastrom.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Thu, Mar 06, 2014 at 08:07:55AM -0500, Rob Seastrom wrote:
>
> Nick Hilliard <nick@foobar.org> writes:
>
> >> haven't you heard about "anycast"??
> >
> > rs probably has. The owner of 199.73.57.122, probably not.
>
> indeed. there are many pieces of evidence that this is not an anycast
> prefix. proof is left as an exercise to those who can perform
> traceroutes from multiple continents, run nmap -sP, log into
> route-views, or do some combination of the above.
>
> -r
>
sorry for the poor attempt at humour...
it was ancient practice to hang many names (not cnames)
off a single IP address. all perfectly legal from a DNS POV.
rs.example.org. in a 10.10.10.53
nick.example.com. in a 10.10.10.53
bbss.isc.org. in a 10.10.10.53
the punchline here was "anycasting" the address across multiple names.
nary a routing trick in sight or in play.
Lame I know.
as a tool to defeat the autobots who insist on "two nameservers"
for a delegation - its kind of a clever poke in the eye w/ a sharp stick.
Back to my oubliette
/bill
