Maybe not such an odd question; Anywhoo, we have quite a few
people who register our IP addresses as nameservers, and then never
delete the records. I don't suppose there is any way that we can delete
these old records, we have appealed to multiple registrars such as
godaddy, enom, and the like to remove these bogus NS records from our IP
space which keep our new customers from using these IP addresses for
hosting but they claim that we have no grounds even though we are the
legitimate 'keepers' of said IP space. This is mainly a problem for
customers who use software such as cPanel which likes to always make NS
records automatically, and customers almost never remove these at their
registrar.
Any thoughts?
-Drew
Maybe not such an odd question; Anywhoo, we have quite a few
people who register our IP addresses as nameservers, and then never
delete the records. I don't suppose there is any way that we can delete
these old records, we have appealed to multiple registrars such as
godaddy, enom, and the like to remove these bogus NS records from our IP
space which keep our new customers from using these IP addresses for
hosting but they claim that we have no grounds even though we are the
legitimate 'keepers' of said IP space. This is mainly a problem for
customers who use software such as cPanel which likes to always make NS
records automatically, and customers almost never remove these at their
registrar.
in named.conf
zone "2.96.192.in-addr.arpa" { type master; file "primary/bogus.ia"; };
in the zone file
* PTR some.schmuck.lame.delegated.to.RAIN.PSG.COM.
or
zone "someschmuck.com" { type master; file "primary/bogus.fwd"; };
and
@ MX 0 some.schmuck.lame.delegated.to.RAIN.PSG.COM.
* MX 0 some.schmuck.lame.delegated.to.RAIN.PSG.COM.
Don't forget:
www IN CNAME goatse.cx
and don't forget the terminating dot on goatse.cx.
but this did cause me to update those trapper zone files and
bump the serials. last time the serials had been bumped since
1995. so you had the suggestion of a decade. mahalo.
randy
> Don't forget:
> www IN CNAME goatse.cx
and don't forget the terminating dot on goatse.cx.
but this did cause me to update those trapper zone files and
bump the serials. last time the serials had been bumped since
1995. so you had the suggestion of a decade. mahalo.
Ouch. So you are going to punish the rest of the world for the mistakes
of a few people (however annoying it is).
/me just cannot imagine explaining this to my mother when she mis-types
some URL.
Granted that what your (former-) customers did was not any sort of best
practice, but I think your "solution" is a little too extreme.
we have appealed to multiple registrars such as
godaddy, enom, and the like to remove these bogus NS records from our IP
space which keep our new customers from using these IP addresses for
hosting but they claim that we have no grounds even though we are the
legitimate 'keepers' of said IP space.
This is a relatively straightforward issue. The registrars
operate according to ICANN policies. Your legitimacy as a keeper
of the IP address space descends from ICANN through IANA.
Either the registrar is in violation of ICANN policy by not
cleaning these NS records, or, the registrar is acting in
accordance with ICANN policy. You need to find out which
is true and then pester ICANN to either police the registars
or fix their broken policy.
I suspect that this is something that is not explicit
in the ICANN registrar agreements but is implied by some
general clause about the wellbeing of the Internet. In that
case ICANN would have to issue an interpretation of the
situation, pointing out to registrars that cleaning stale
NS records is, in fact, part of their ICANN agreement.
http://www.icann.org is the place to go.
--Michael Dillon