You can rename the nameserver to something else, thereby releasing the
www.yahoo.com name from being an issue.
----- Original Message -----
From: "Derek J. Balling" <[EMAIL PROTECTED]>
To: "Eric Paynter" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Saturday, October 27, 2001 2:32 PM
Subject: Re: Removing Nameservers
> What if you want the hostname to point at, say, 30 servers, because you're
big.
>
> For example, what if yahoo.com had made a mistake way back when and
> had primary Ns on "www.yahoo.com". Someone else "points at it
> hostilely", meaning that "www.yahoo.com" is stuck, in the roots, with
> a single IP. Even though they really need to load-balance that
> traffic evenly across {N} machines.
>
> They'd like to delete it (hypothetically), but can't.
>
> How do they go about getting the other records disassociated from the
> host, so they can get the host deleted? It seems there's a flaw in
> the logic, because it allows folks other than the owner of the host
> to control the fate of the host.
--
The nice thing about standards, there is enough for everyone to have their own.
