If the domain is in use, create a zone file with an extremely long TTL aliasing * to 127.0.0.1. If it's a domain they are using, and are trying to use your NS server without your permission, you'll fix 'em up real quick.
Also keep in mind, you can change the IPs or the name of the nameserver, so if you're moving away from a single server and changing to dedicated NS servers, you can just rename the server and the immediate problem is resolved. ----- Original Message ----- From: "Derek J. Balling" <[EMAIL PROTECTED]> To: "Genie" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Saturday, October 27, 2001 11:53 AM Subject: RE: Removing Nameservers > On a similar note, is there any way to force "hostile" domains to > drop your nameserver so you can kill it? > > e.g., if I wanted to prevent ns1.foo.com from ever being deleted, I > could simply add it (lamely) to my domain's NS-set. > > The hostile usefulness of this is most evident where the host record > in question starts with "www." and the company now wants a dedicated > nameserver. -- The nice thing about standards, there is enough for everyone to have their own.
