Looks like someone forgot to renew there domain name and another party
decided to do it for them, with some slight changes:
host 206.108.102.93
93.102.108.206.in-addr.arpa domain name pointer
bells-network-has-lots-of-security-holes-to-exploit.bell-nexxia.net
This isn't a lapsed domain registration issue; we're not talking about A
records. It doesn't strike you as odd (read 'a security issue') that the
PTR records have been changed?
Looks like someone forgot to renew there domain name and another party
decided to do it for them, with some slight changes:host 206.108.102.93
93.102.108.206.in-addr.arpa domain name pointer
bells-network-has-lots-of-security-holes-to-exploit.bell-nexxia.netThis isn't a lapsed domain registration issue; we're not talking about A
records. It doesn't strike you as odd (read 'a security issue') that the
PTR records have been changed?
It is absolutely a lapsed domain issue. The authoritive (arpa) servers for the netblock in question (and several other bell blocks) are taz and pluto.bell-nexxia.net
I registered it last year (after getting sick of waiting for lookups to timeout on traceroutes), created the proper glue records to the original NS's and tried to give it back to bell via all available channels, nobody seemed to care, so I let it expire.
Looks like someone forgot to renew there domain name and another party
decided to do it for them, with some slight changes:host 206.108.102.93
93.102.108.206.in-addr.arpa domain name pointer
bells-network-has-lots-of-security-holes-to-exploit.bell-nexxia.netThis isn't a lapsed domain registration issue; we're not talking about A
records. It doesn't strike you as odd (read 'a security issue') that the
PTR records have been changed?
It is absolutely a lapsed domain issue. The authoritive (arpa) servers for the netblock in question (and several other bell blocks) are taz and pluto.bell-nexxia.net
I registered it last year (after getting sick of waiting for lookups to timeout on traceroutes), created the proper glue records to the original NS's and tried to give it back to bell via all available channels, nobody seemed to care, so I let it expire.
It is absolutely a lapsed domain issue. The authoritive (arpa)
servers for the netblock in question (and several other bell blocks)
are taz and pluto.bell-nexxia.net
My mistake; replied too hastily.
I registered it last year (after getting sick of waiting for lookups
to timeout on traceroutes), created the proper glue records to the
original NS's and tried to give it back to bell via all available
channels, nobody seemed to care, so I let it expire.
I would hope that this would get their attention, but after your
attempt, I won't hold my breath. Thanks for clarifying.
Well, a PTR can point *anywhere* as long as you control the zone. The only
thing that made it remotely interesting was this SOA:
102.108.206.in-addr.arpa. 0 IN SOA pluto.bell-nexxia.net. help.bell-nexxia.net. 2003110400 28800 7200 604800 86400
It's interesting that googling for 'bell-nexxia.net' doesnt actually hit anything.
Who did you THINK owned that domain and address space?
Bell's ARIN records show 102.108.206.in-addr.arpa delegated to nameservers named under bell-nexxia.net, which is a zone that Bell do not currently run.
If you believe the dates returned by whois.crsnic.net, "bell-nexxia.net" was only recently registered, while "bellnexxia.net" was registered in 1999.
Maybe someone at Bell typo'd nameserver names when they filled out the paperwork for 206.108/20, and someone else got fed up with waiting for them to fix it (and hence the reverse DNS for these blocks).
Joe