With the recent and only somewhat confirmed removal of POC information
from the Internic Whois database, and the upcoming set of newcomers to the
field, will we perhaps see a return or rise to popularity of RP dns
records?
Having your nameserver be able to dole out contact information for your
domains, site, and hosts is a nice alternative to having no source of this
information. Unfortunately, if your nameserver(s) are down when someone is
trying to contact you, the effort is futile.
The two biggest things that made whois useful in locating contact
information were that EVERY domain in the Internic-controlled TLD's had
contact information in Whois by requirement of Internic- and the database
somewhat centralized. There were multiple whois servers with all the
information, and you were usually able to obtain that information even if
network connectivity to a site was down.
As whois becomes less and less useful, we may find ourselves seeking
sanity in RP records. Unfortunately, it would appear that this is a
mediocre solution at best.
file this one under thoughts, random.
-jeff
Jeff Godin
Network Specialist
Traverse Area District Library / Traverse Community Network jeff@tcnet.org - 616/932-8546 voice
Yes, POC of information in dns, soa records, etc.. is useful.
Problem is severe lack of clue with people running dns. This
can not be easily fixed.
ex:
query(139.221.36.200.in-addr.arpa) All possible A RR's lame
query(14.0.208.209.in-addr.arpa) All possible A RR's lame
query(142.105.230.200.in-addr.arpa) All possible A RR's lame
query(152.104.230.200.in-addr.arpa) All possible A RR's lame
query(5.241.226.207.in-addr.arpa) All possible A RR's lame
query(78.254.185.209.in-addr.arpa) All possible A RR's lame
query(TN-56K-1.tamnet.com.mx) All possible A RR's lame
query(TN-56K-172.tamnet.com.mx) All possible A RR's lame
query(TN-56K-173.tamnet.com.mx) All possible A RR's lame
query(cajunemail.com) All possible A RR's lame
query(gate7.olympiakos.com) All possible A RR's lame
query(geocites.com) All possible A RR's lame
query(hotmail.net) All possible A RR's lame
query(mail.hotmail.net) All possible A RR's lame
query(worldnet.com) All possible A RR's lame
query(writeme.net) All possible A RR's lame
/sigh
Registrant:
Nether Network (NETHER-DOM)
2738 Eastlawn
Ypsilanti, MI 48197
US
Aha. As I had stated, the removal was only "somewhat confirmed". Perhaps I
was a bit premature in my thoughts.
Yes, POC of information in dns, soa records, etc.. is useful.
Problem is severe lack of clue with people running dns. This
can not be easily fixed.
Indeed. That is why Whois is so useful. It more-or-less requires that
each domain have contact information in a proper form, etc. I'm not sure
how I feel about the Clueless NIC leading the Clueless users, though...
-jeff
Jeff Godin
Network Specialist
Traverse Area District Library / Traverse Community Network jeff@tcnet.org - 616/932-8546 voice
segue appears to be the problem. Right before the batch o'dupes, I got
half a dozen messages with hop count exceeded, and segue.merit.edu
figured prominently.
The problem was a subscriber at raytheon (via ti, via paranet). From the
headers I've seen it looks like mail for him started getting backed up
on one raytheon machine last week and apparently when the destination
machine came back up today it all started getting spewed back to the
list. Right around 5:00 p.m. EST, we dropped him from the list and put
in a filter to stop these messages, but a lot had already been queued.
In the future, majordomo will be inserting an "X-Loop: nanog" header and
stopping any messages that already have that. (Thanks Daniel.)
Sorry for the inconvenience, and thanks to all who took the time to send
a heads-up.
