On Fri, 27 Oct 2006, Peter Mott wrote:

On 27/10/2006, at 3:23 PM, Mark Foster wrote:

...

Ask them do a whois on the domain, and then point out that if they are carrying Authoritive NS records for a domain which the rootservers are pointing elsewhere - whois tells you this - they are breaking the DNS.

One could also encourage folks to use different name servers for caching and not allow recursion on their authoritative servers. That way if they claim to be authoritative and they are no longer, nobody cares.

I seem to remember having a discussion about this very thing with a large provider about 6 years ago and they were not interested in any form of co-operation that would prevent client internet experience being broken when a change of delegation took place. They didn't have the capacity to understand the problem let alone a resolve to solve it. I wonder if anything has changed :-)

Actually a possible 'reason' for this just occurred to me. If you're buying a DNS hosting service from an ISP, does the ISP have the right to cancel said hosting service without authority from the customer? This, I believe, has been a cited reason _not_ to remove legacy DNS (despite what the registry says) for at least one provider i've heard of before now. It makes the issue one of customer-provider liason - and one of monetary/commercial significance - instead of dns/operational significance. I favour the latter. But there may be a valid point here... Mark.