In this case, why not just remove the nameservers? It can't possibly matter that myemployer-sucks.com shows up in the whois but doesn't go anywhere.
In fact, many companies register such names to prevent others from using them. Hey, a revenue opportunity! Deleting? You should be renewing these domains!!! :) Dave Warren wrote: > > > There are lots of good reasons a registrant may want to cut a domain name > > loose immediately (such as discovering it infringes the trademark of a > > litigious company). Granted, they can change the contact details to > > something completely bogus, but that is technically not allowed (and may > not > > be sufficient). > > Or discovering someone, as a joke, registered myemployer-sucks.com under my > email address and contact information. I just requested the password, it > was emailed to me, and I changed the information to some bogus info right > away, but not before my ass was kicked at work by management. > > They have no interest in keeping the domain (It's actually a play on words, > we already own the -sucks version of the name, and it was decided that > keeping one play on words would be bad, if someone discovered it, they might > think of other variations), and I was asked to delete it. This was, of > course, not possible. > > There are situations where deletions have a certian use... > > -- > The nice thing about standards, there is enough for everyone to have their own. -- Robert Rivers OpenSRS Technical Operations http://www.opensrs.org/Support_FAQ.shtml
