[77209] in North American Network Operators' Group
Re: fwd: Re: [registrars] Re: panix.com hijacked
daemon@ATHENA.MIT.EDU (Joe Maimon)
Sun Jan 16 14:48:59 2005
Date: Sun, 16 Jan 2005 14:45:42 -0500
From: Joe Maimon <jmaimon@ttec.com>
To: Andrew Brown <twofsonet@graffiti.com>
Cc: William Allen Simpson <wsimpson@greendragon.com>,
nanog@merit.edu, "Ross Wm. Rader" <ross@tucows.com>
In-Reply-To: <20050116134006.A22070@noc.untraceable.net>
Errors-To: owner-nanog-outgoing@merit.edu
Andrew Brown wrote:
>On Sun, Jan 16, 2005 at 07:21:55PM +0100, Daniel Karrenberg wrote:
>
>
>>On 16.01 12:46, William Allen Simpson wrote:
>>
>>
>>>>------- Forwarded Message
>>>>
>>>>From: "Ross Wm. Rader" <ross@tucows.com>
>>>>
>>>>
>>>>I don't see what you are looking at - .net and .com point to the same
>>>>place with no indication of anything awry...of course, I'm late to the
>>>>game and the DNS probably tells a different story...
>>>>
>>>>
>>>>
>>>>
>>>>
>>>This fellow is pretty confused, as from here (Michigan via Merit) the
>>>DNS has pointed to different places since yesterday.
>>>
>>>
>>A quick survey of some caching servers in my neighborhood reveals that
>>some of them return "old/correct" A RRs for panix.com at this time.
>>
>>
>
>presumably they have cached ns records from before the switch in the
>com tld zone.
>
>
>
Thus justifying those who load their NS and corresponding NS's A records
with nice long TTL
At least those whose caches' your still in will still talk to you after
your registrar screws you.
(OT
Limiting named cache size could have an adverse effect for people hoping
to cash into this inusurance. Shouldnt cache limiting kill low priority
records such as A's which do not correspond to cached NS first....
)
