I have IP address space. An address in that address space is listed as
a host record for a fair number of domains that are not mine. Hence, DNS
requests come to that address. But I cannot delete the host record, because
there are domains using it.
Is there a magic contact somewhere at Network Solutions that can fix this?
Matthew Kaufman
matthew@eeph.com
Is there really an appreciable amount of traffic being caused by this?
Anyway, only your registrar can delete host records. If Network Solutions is
your registrar, then they can do it. If they refuse (due to the host being
in use), then your best bet might be to change it to another address,
possibly one you've null routed.
--Adam
I went through this with NetSol a while ago. It's a pain in the neck, but
they will get it done, eventually. First you have to call them and sit on
hold and get transfered for about 3 days, and get a list of all domains
which use this nameserver. Then, you send them a fax on letterhead saying
that those domains were never authorized to use that nameserver, etc, etc,
etc. Eventually, your nameserver will be removed from those domains and you
can then delete it. Whole process ended up taking about 2 months for me.
Jeff
Must be nice. The entire process took 6+ years for us.
And it's not entirely true that "only your domain registrar has host
records for your domain". We recently transferred the affected domain
from Netsol to another registry, but Netsol failed to delete the host
record. Then, when called about it, they first said we had to get the
domain list (which we have requested, literally, about a hundred times
over the years, and never gotten), or, more recently, that it wasn't even
in their database!
Finally it took threats of lawsuits (don't look at me, that wasn't my
idea. My boss is whacked out, he likes to threaten people like that way
too much for his own good), but it disappeared.
I still think my idea of submitting an IP change for the host record to a
non-useable address (I was leaning towards 127.0.0.1, but RFC1918 addrs
will work just fine, too) would have been more effective. But, c'est la
vie.
-j
You're right, but that's not what I said.
I guess the completeley technically correct statement in this case would have
been "only your registrar is able to create, delete, and modify your host
records in whois.internic.net, and hence, your nameservers' glue records in
the GTLD servers".
Another registrar could do whatever it wants with its own database, and
that's exactly what NSOL does. The only way to fix this is to do your part
to make NSOL 'shape up or ship out'. Transfer your domains to other
registrars and encourage your customers to do the same.
--Adam
At this time no registrar can delete host records. What they do is
transfer your host into another specifially reserved domain, for example
NSI uses LAME-DELEGATION.ORG, so if you had ns1.somedomain.com, it would
become LAME99999.LAME-DELEGATION.ORG. Other registrars have their own
domains for such domains (for example opensrs is NS-NOT-IN-SERVICE.COM).
Usually hosts are transfered into these domains before domain is deleted
(for non-payment) but if you talk to your registrar (which is difficult
with NSI...), their engineers can do it with active domains too.
Finally it took threats of lawsuits (don't look at me, that wasn't my
idea.
I hear that, all things considered, a credible threat to sue is the
most cost-effective way to get NSI to do something. I once got them
to fix a broken domain entry by telling them (truthfully) that I was
revising the domain registration section of a large Internet book and
was planning to tell people that it was impossible to get NSI to fix
problems, but I don't think I can do that very often.
Last time I wanted this done, it took about an hour or two before I
got confirmation and it was gone the next day (thanks Joe!).
That said, I'm using OpenSRS so if that's the difference and it really
does take weeks or worse... well, you can figure it out 
--cw