Internic hosage (fwd)

Dalvenjah,

Thanks for your feedback. Network Solutions served over
35 million WHOIS queries in the month of January 1998.
The average response time for our WHOIS service is less
than 5 seconds per query.

Thank you for the statistics. Not sure of their applicability, but it's
nice to know just how heavily used this database is. Hmmm...one would
think that if it's that heavily hit, maybe there would be some interest in
keeping it accurate, yes?

Please keep in mind that Network Solutions is not the
registry for the .to domain. We recommend you contact
the Tonic registry for information about .TO domain names.
Their web site is www.tonic.to

And it's the Kingdom of Tonga's domain, for which Tonic is merely the
Registry.

However, the point has been completely missed here, Eric. The point Dal
was making is that Perhaps.youwant.to FALSIFIED, LIED, FORGED, STOLE,
MISAPPROPRIATED, and otherwise BS'd about their WhoIs entry:

[No name] PERHAPS-HST

   Hostname: PERHAPS.YOUWANT.TO
   Address: 205.166.250.10
   System: ? running ?

   Coordinator:
      HOST Networks-DNS Administration HNA-ORG hostmaster@HOST.NET
      800-697-2437
Fax- 800-697-2437

   Record last updated on 16-Mar-98.
   Database last updated on 20-Mar-98 04:11:54 EDT.

[perhaps.youwant.to]
Translated Name: perhaps.youwant.to
IP Address: 207.89.50.3

Internet Gateway Connections (NETBLK-IGC-FL-BLK-1)
        10011 Pines Boulevard - Suite 203
        Pembroke Pines, Florida 33024

        Netname: IGC-FL-BLK-1
        Netblock: 207.89.0.0 - 207.89.127.255
        Maintainer: IGCN

        Coordinator:
           Master, Host (HM511-ARIN) mike@WEB2000.NET
           305-655-2955 (FAX) 305-652-5090

        Domain System inverse mapping provided by:

        NS3.WEB2000.NET 207.89.0.10
        NS4.WEB2000.NET 207.89.0.30

        Record last updated on 17-Aug-96.
        Database last updated on 19-Mar-98 16:08:42 EDT.

Traceroute confirms that youwant.to is hosted by Web2000.net. The
WhoIs-listed IP is user.host.net, the machine on which Host.Net runs their
webpage, FTP, et al. Not real likely they'd give that out for a hosted
domain's IP.

So....four days ago, youwant.to [side issue: Why does a machine,
"perhaps", have a host entry in WhoIs, but the domain, "youwant.to" not?]
updated their WhoIs record with a bunch of lies. THAT is the point, and
the problem. What is NSI/InterNIC going to do about it, Eric?

Regards,

Eric Eden
Senior Analyst Network Solutions, Inc.
Phone: 703-925-6710 erice@internic.net

Spam: it's not just for breakfast anymore....

Dean Robb
PC-Easy
On-site computer services
(757) 495-EASY [3279]

On Fri, Mar 20, 1998 at 01:45:56PM -0500, Dean Robb put this into my mailbox:

However, the point has been completely missed here, Eric. The point Dal
was making is that Perhaps.youwant.to FALSIFIED, LIED, FORGED, STOLE,
MISAPPROPRIATED, and otherwise BS'd about their WhoIs entry:

[...]

So....four days ago, youwant.to [side issue: Why does a machine,
"perhaps", have a host entry in WhoIs, but the domain, "youwant.to" not?]
updated their WhoIs record with a bunch of lies. THAT is the point, and
the problem. What is NSI/InterNIC going to do about it, Eric?

I wish to point out that I know the owner of the 'youwant.to' domain; he
had nothing to do with installing the WHOIS entry. Someone else evidently
decided it would be a good idea to falsify an InterNIC host record (for
god knows what reason) and submit it. youwant.to is a personal domain,
not a haven for spammers or anything of the sort.

My point in bringing this up was to show how someone can basically submit
entirely bogus information to InterNIC, and they don't even have a simple
sanity check such as an 'nslookup <addr>' to confirm that the IPs match.
This should have at least triggered a flag and perhaps a mail to somebody.
It didn't, and is now in WHOIS, and quite probably the root nameserver
glue, as well. Woe betide my friend if he'd like to use that as a nameserver
for a domain of his someday.

-dalvenjah

It seems you upset that there is a foreign domain hosted in the US, and
that there is a probably useless and incorrect host record in the whois
database. There is nothing terribly wrong with this.

You seem to be assuming that hosting a foreign-registered domain in the US
is evidence of some kind of deception or conspiracy. I just don't see any.
Indeed, I just registered youdontwant.to via the Tonic registry. No
deception. Perhaps I'll track anti-spam terrorism on
perhaps.youdontwant.to. :wink: **
Unfortunately, Tonic doesn't seem to have a whois server. In any case,
Internic doesn't have anything to do with it. As Eric said, but you won't
accept.

Whois Host records are informational, until they are entered into a domain
record. In a domain record, they give one a nice tool to update the
nameservers of many hosted domains with only update. There isn't any way to
check them on creation. You can only authenticate updates to the records.
Given that ARIN runs a whois server and Tonic doesn't explains why there is
a host record but not a domain record (except in DNS). Whois Host records
only have effect once their handle is entered into the domain record.
Updates to the host record are also usually authenticated in simple or
sophisticated ways. But again, the domain record is owned by Tonic, not
Internic, so complaints to Internic will not be useful, or effective.
Tonic, incidentally, does appear to have working password authentication on
its domain updates. Tonic assigns handles separately from Internic, so the
existance of host record in another registry doen't mean it could be
accidentaly put into the domain record. This host information may be in
fact be wrong or just useless or just informational but whatever the case,
it doesn't have any effect on anything.

While a bogus host record could possibly be some foolish failed attempt at
spoofing the domain, it could also (more likely) be the remnants of some
past or future association. In this particular case, I'd bet that someone
incorrectly added a host record to Internic, instead of Tonic, by simple
mistake. The owner of the domain probably knows which. Its mere existance
doesn't mean anything conspiratorial is going on. Perhaps a quiet message
to the domain owner noting this looks a bit crufty might be nice. But there
is nothing for either Internic or Nanog to do. If its conspiracy you are
looking to expose, your time is probably better spent looking for the
second iceberg that really sank the Titanic.

While there are perhaps real complaints to be made about Internics
authentication, this is not an example of one of them.

    --Dean

** (Seriously, I did mean to follow-up the anti-spam terrorism thread last
week--If people email me privately, I will try to organize tracking of
anti-spam criminal activities. I also want to organize a group of
moderates to advocate rational laws regulating spam. Many of the people who
are talking with legislators right now are radicals or just ignorant. We
really need some moderates to get involved. As you can see, there are some
very misguided people out there talking to even more ignorant people in the
Press and in Legislative bodies.)

Most excellent. Now, what would you have done if it was Dirtbag.com that
had provided the false information?

Spam: it's not just for breakfast anymore....

Dean Robb
PC-Easy
On-site computer services
(757) 495-EASY [3279]

[snip]

You seem to be assuming that hosting a foreign-registered domain in the US
is evidence of some kind of deception or conspiracy. I just don't see any.
Indeed, I just registered youdontwant.to via the Tonic registry. No
deception. Perhaps I'll track anti-spam terrorism on
perhaps.youdontwant.to. :wink: **
Unfortunately, Tonic doesn't seem to have a whois server. In any case,
Internic doesn't have anything to do with it. As Eric said, but you won't
accept.

Try reading again. I have no problem, nor did I imply a problem, with
foreign hosts having listings in InterNIC. The 'Net IS worldwide, after
all. I cannot imagine where you get the idea that I "won't accept" this
concept. And if you read Tonic's webpage, you'll see that there is a
database at www.tonic.to/whois?xxxxxx.to (xxxx being the domain in
question). Tonic's WhoIs doesn't provide a contact info, but it does
provide server and IP info. Sorry, Dean...your anti-spammer bias seems to
be coloring your comments.

[snip comments based on erroneous premise of no WhoIs at Tonic]

existance of host record in another registry doen't mean it could be
accidentaly put into the domain record. This host information may be in
fact be wrong or just useless or just informational but whatever the case,
it doesn't have any effect on anything.

Actually, you're quite wrong. SEVERAL RFCs require accurate information in
the WhoIs database, NSI's Registration Agreement requires it and WhoIs is
heavily used to contact domains/networks for various reasons (some quite
important). The point and problem is that NSI (with this one, notable,
exception) does nothing when presented evidence of falsified data in WhoIs.
  Now...what good is a database with known inaccuracies?

As to verification, I can't think of an easy, effective way to verify the
template information when presented for domain registration. However, when
lies and false information in that registration is pointed out, NSI has an
obligation to take action as provided for in the signed Registration
Agreement.

While a bogus host record could possibly be some foolish failed attempt at
spoofing the domain, it could also (more likely) be the remnants of some
past or future association. In this particular case, I'd bet that someone
incorrectly added a host record to Internic, instead of Tonic, by simple
mistake. The owner of the domain probably knows which. Its mere existance
doesn't mean anything conspiratorial is going on. Perhaps a quiet message
to the domain owner noting this looks a bit crufty might be nice. But there
is nothing for either Internic or Nanog to do. If its conspiracy you are
looking to expose, your time is probably better spent looking for the
second iceberg that really sank the Titanic.

Actually, there is strong evidence that a significant percentage of the
incorrect information in WhoIs is there deliberately...inserted by
net.abusers trying to avoid identification. There may be a large number of
just plain errors, too...so why is nothing done to try to clean up the
database?

A nice quiet message to the person who registered MartianConsulate.com and
listed a phone number of 555-1212 isn't likely to do much; nor will a
polite email to the person who registered his contact info as
"HeadHoncho@no.such.domain". THESE are the folks that need to be deleted.

As for nothing InterNIC or NANOG can do: It is NSI's job to administer the
database. Ensuring valid data is part of administration of a database.
NANOG member interface and work with NSI daily...who better to help them
get their act together? Or do you really want to be the one deluged with
flamemail because some spammer listed your server as his?

** (Seriously, I did mean to follow-up the anti-spam terrorism thread last
week--If people email me privately, I will try to organize tracking of
anti-spam criminal activities. I also want to organize a group of
moderates to advocate rational laws regulating spam. Many of the people who
are talking with legislators right now are radicals or just ignorant. We
really need some moderates to get involved. As you can see, there are some
very misguided people out there talking to even more ignorant people in the
Press and in Legislative bodies.)

Ah...now the agenda becomes more clear. Guess what? I'm an anti-spammer
and have never hacked anything other than wood in my life. NANOG is
definately inappropriate for us to discuss our differences in opinion, but
you're webpage "Stupid Laws" section shows you to not believe that spam
hurts anyone. Guess ACSI didn't really sue ConnectUp over spam; AOL, GTE
and @Home didn't really have mail servers crash from spamloads; none of the
backbones prohibit spam; RFC 1855 doesn't abjure the sending of unsolicited
email; and there's no problem with spam.

Maybe all those who don't like spam should just email you privately (at
this or your dawg@world.std.com [you know, the one you send unsolicted
commercial email aka spam from] address?)?
Spam: it's not just for breakfast anymore....

Dean Robb
PC-Easy
On-site computer services
(757) 495-EASY [3279]

Try reading again. I have no problem, nor did I imply a problem, with
foreign hosts having listings in InterNIC. The 'Net IS worldwide, after
all. I cannot imagine where you get the idea that I "won't accept" this
concept.

Oh. I see. You didn't write this:

Dean Robb:
Traceroute confirms that youwant.to is hosted by Web2000.net. The
WhoIs-listed IP is user.host.net, the machine on which Host.Net runs their
webpage, FTP, et al. Not real likely they'd give that out for a hosted
domain's IP.

Sounds pretty conspiratorial to me. It is indeed very "likely" that they'd
give out a host record user.host.net for a hosted domain's IP. There is
absolutely nothing wrong with that.

Dean Robb:
So....four days ago, youwant.to [side issue: Why does a machine,
"perhaps", have a host entry in WhoIs, but the domain, "youwant.to" not?]
updated their WhoIs record with a bunch of lies. THAT is the point, and
the problem. What is NSI/InterNIC going to do about it, Eric?

So your "side issue" above is completely untrustworthy. I admit, I just
tried whois -h www.tonic.co. I should have looked at the web page. I am
wrong about them not having a whois page.

The correct answer, is that the Internic is not, can not, and will not do
anything about it until they are asked by someone authoritative. And you
aren't that. Look for conspiracies where you will.

Actually, there is strong evidence that a significant percentage of the
incorrect information in WhoIs is there deliberately...inserted by
net.abusers trying to avoid identification. There may be a large number of
just plain errors, too...so why is nothing done to try to clean up the
database?

I think that Internic gets paid. Thats pretty strong "correct" information.
Anyway, there is not a real database on the planet that has entirely
correct information. In this case, the incorrectness of the information is
trivial, and has no effect on anything. No one can hijack a domain from
another registry this way.

As for nothing InterNIC or NANOG can do: It is NSI's job to administer the
database.

Several people have said this. I've said it several times: Its Tonic's
database, not Internics. Being such a simple concept, nothing more really
needs to be said.

Second, and several people have also confirmed this as well, the incorrect
host record may be just innocently incorrect. It's not your concern. Its
not nanogs concern. In fact, Internic can't tell whether the real owner of
perhaps.youwant.to owns that ip address or not. If they don't own it, they
can complain to Internic about it. But you can't. It doesn't belong to you.

There is no conspiracy to conceal information. There is no conspiracy by
Internic to enable hijacking domains and populate their database with
incorrect information.

Maybe all those who don't like spam should just email you privately (at
this or your dawg@world.std.com [you know, the one you send unsolicted
commercial email aka spam from] address?)?

This is a good example of anti-spammer terrorism. Mr. Robb here appears to
encourage annoying or hate mails to a private account, and slander me with
hate mail. I rarely send mail from that account, and never publicly. It
must have taken some research for Mr. Robb to find that address. This, in
fact, is inappropriate behavior.

I have to question whether its appropriate for Mr. Robb to be on the Nanog
list.

I have had my World account for 7 years. Barry Shein (owner of world) is
probably one of the most vehement and active anti-spam activists there are.
I think he reads this list, and I hope he will attest that I have never
sent spam from his system.

Fortunately, Barry can distinguish political activism from terrorism.
Indeed, he is one of the innocent victims of anti-spammer terrorism. He has
suffered through bonafide denial of service attacks, unable to get the
FBI's attention, because they seem to involve spam, and 99% of all spam
complaints are frivolous

    --Dean

Eric Eden, Internic:
In this case we removed the host and notified the contact of the
host because it is not currently serving any domain names or
networks in our database.

[Not because there was anything "false" about it. It is still served up by
Tonic]

Dean Robb:
Most excellent. Now, what would you have done if it was Dirtbag.com that
had provided the false information?

I have to question why people intentionally supply false information.
Perhaps to avoid harassment from radical and misguided people? I have to
presume in this case that Mr. Robb considers himself the sole judge of
appropriateness of the entity. Given that youwant.to was perfectly legit,
except for some cruftiness, I don't think we can really trust his judgement
on such matters.

This brings up an issue with whois databases that is relevant to nanog:
Who should have access to whois contact information and its misuse.

Perhaps we need to have a way to authenticate and limit who can get phone
numbers and email addresses from the whois database, in order to prevent
the kind of harassment and abuse apparently exercised by Mr. Robb.

    --Dean

I think that this is a really important issue. Thanks for bringing it
up.

Who should have access to whois contact information and its misuse.

I put my data in there for use by folk with net ops problems. My
understanding is this is the purpose for which whois data have always
been given.

randy

I don't see how you can possibly cut this off.

I hate the people who abuse this data too. One way to cut it down is to
accept only direct matches (ie: no more "wildcarding").

This also makes the database search engine incredibly simple and fast, as
opposed to complicated and slow.

Finally, it probably solves 90% of the abuse issues.

Try reading again. I have no problem, nor did I imply a problem, with
foreign hosts having listings in InterNIC. The 'Net IS worldwide, after
all. I cannot imagine where you get the idea that I "won't accept" this
concept.

Oh. I see. You didn't write this:

Dean Robb:
Traceroute confirms that youwant.to is hosted by Web2000.net. The
WhoIs-listed IP is user.host.net, the machine on which Host.Net runs their
webpage, FTP, et al. Not real likely they'd give that out for a hosted
domain's IP.

Sounds pretty conspiratorial to me. It is indeed very "likely" that they'd
give out a host record user.host.net for a hosted domain's IP. There is
absolutely nothing wrong with that.

1. Your interpretation of "conspiratorial" is completely outside the realm
of your initial statement that I had a problem with foreign hosts in
InterNIC. The words you quoted also don't support your opening assertion.
Please look up "relevant" in the dictionary.

2. Conspiracy requires two or more persons to engage in an activity
together. My point was that the person who registered youwant.to lied to
InterNIC. One person cannot be a conspiracy. Please look up "conspiracy"
in the dictionary.

3. Do you register domains you host as domain.av8.com? If so, please go
re-read the RFCs to see how to properly list a hosted domain. The
registration was not that of a proper domain, nor is it hosted by Host.net
as the registration claimed.

Dean Robb:
So....four days ago, youwant.to [side issue: Why does a machine,
"perhaps", have a host entry in WhoIs, but the domain, "youwant.to" not?]
updated their WhoIs record with a bunch of lies. THAT is the point, and
the problem. What is NSI/InterNIC going to do about it, Eric?

So your "side issue" above is completely untrustworthy. I admit, I just
tried whois -h www.tonic.co. I should have looked at the web page. I am
wrong about them not having a whois page.

1. Untrustworthy? Somehow, I don't think that's the word you were looking
for. Sadly, there's no way to know what word you were looking for as the
point was that the registration was in the standard form for a machine
name, not a domain name and you didn't dispute that.

The correct answer, is that the Internic is not, can not, and will not do
anything about it until they are asked by someone authoritative. And you
aren't that. Look for conspiracies where you will.

1. Please, Oliver Stone, Jr....quit talking of conspiracies. The only
conspiracy around here is your determination to use the word as often as
possible. InterNIC...and any other registry or network operator...should
investigate ANY report of a problem. There is no RFC, statutory nor
intelligent reason that the reporter need be "someone authoritative".

2. Assuming that for some reason unknown, a reporter of a problem must be
"authoritative"...who would qualify? A system administrator? A sysadmin
with over 100 systems? CEO of an ISP?

3. You know nothing of my qualifications, job or anything else. How do
you know I'm *not* authoritative?

4. In fact, InterNIC DID remove the domain. Apparently, someone hijacked
the name when he registered with InterNIC from the REAL youwant.to owner
for reasons unknown.
Apparently, NSI doesn't agree with your stance.

net.abusers trying to avoid identification. There may be a large number of
just plain errors, too...so why is nothing done to try to clean up the
database?

I think that Internic gets paid. Thats pretty strong "correct" information.
Anyway, there is not a real database on the planet that has entirely
correct information. In this case, the incorrectness of the information is
trivial, and has no effect on anything. No one can hijack a domain from
another registry this way.

1. How does "paid" equal "correct information"? That's probably the most
illogical, of many, thing you've said.

2. Do you assert that because no database has entirely correct information
that no effort should be made to clean up the WhoIs database?

3. In this case, it is a fairly minor issue. However, it exemplifies a
major problem: false information in InterNIC registrations that NSI
refuses to do anything about.
I note that you fail to address that issue...the whole point...the
problem...in any manner whatsoever.

As for nothing InterNIC or NANOG can do: It is NSI's job to administer the
database.

Several people have said this. I've said it several times: Its Tonic's
database, not Internics. Being such a simple concept, nothing more really
needs to be said.

1. Please...try to keep up here. The false information is in WhoIs, the
InterNIC database administered by Network Solutions, Inc, found at
http://rs.internic.net/cgi-bin/whois. Being such a simple concept, surely
you can understand that.

Second, and several people have also confirmed this as well, the incorrect
host record may be just innocently incorrect. It's not your concern. Its
not nanogs concern. In fact, Internic can't tell whether the real owner of
perhaps.youwant.to owns that ip address or not. If they don't own it, they
can complain to Internic about it. But you can't. It doesn't belong to you.

1. Of course it's perfectly innocent! The registrant accidently typed in
the correct IP of another network, one that he is *not* hosted on, along
with it's name. Perfectly understandable accident.

2. I'll type it slowly: if the domain is not at the IP address listed, and
if it's not hosted by the listed DNS servers, then it's a pretty safe bet
that they don't own the listed IP.

3. Ah, I see. Using your logic, then, only a police officer should report
a crime; only a firefighter should own a fire extinguisher; only a domain
owner should talk to InterNIC. Really,
Dean...http://ds.internic.net/ds/dspg1intdoc.html. For someone so gung-ho
on the rights of people, you sure seem convinced that I don't have a right
to complain.

There is no conspiracy to conceal information. There is no conspiracy by
Internic to enable hijacking domains and populate their database with
incorrect information.

Whoever said there was? Large numbers of net abusers (including [gasp!]
spammers) falsify their registrations. InterNIC isn't part of any
conspiracy, they just don't enforce their contract nor do they properly
administer their database. What is your fascination with conspiracies?

This is a good example of anti-spammer terrorism. Mr. Robb here appears to
encourage annoying or hate mails to a private account, and slander me with
hate mail. I rarely send mail from that account, and never publicly. It
must have taken some research for Mr. Robb to find that address. This, in
fact, is inappropriate behavior.

Ah, a fine example of how anyone who doesn't agree with you is an
"anti-spammer terrorist". I'm merely trying to clarify at which of your
public addresses you want people to contact you. Please, do tame that
jerking knee. No one said "slander", "flame" or anything else.

As for the "research", YOU ARE AN IDIOT AND A LIAR. The "research" I did?
I visited your website: http://www.av8.com. I visited a page on your
website: http://www.av8.com/H.4581/how.html. I read a sentence near the
bottom of the page: "I began my consulting service using an account on
"world.std.com", which I still have (I'm dawg@world.std.com). I sent out
email to customers, and potential customers of my services."

By your own admission, you send unsolicited commercial email from that
account. Since you elsewhere indicate that address harvesting is
appropriate behavior, then what have I done wrong?

I have to question whether its appropriate for Mr. Robb to be on the Nanog
list.

Sorry. You don't own the list, you can't complain. Your logic, sir...and
your petard.

[snip]

Indeed, he is one of the innocent victims of anti-spammer terrorism. He has
suffered through bonafide denial of service attacks, unable to get the
FBI's attention, because they seem to involve spam, and 99% of all spam
complaints are frivolous

Now, provide some real facts, please. Where do you get your percentages?
What qualifies a complaint as "frivolous"? Explain why Mr. Shein was
unable to pick up the phone and call the FBI. Your assertion is also
illogical...if Mr. Shein was an innocent victim, why is he an active
anti-spam activist (oh, redundancy!).

My dear Mr. Anderson...you have an axe to grind, and fact/reality won't
sway you. You also can't argue logically, as the above proves. Since you
have proven yourself a fool, and I have no time for fools, I'll not respond
to any further silly things you want to say. The questions posed are
rhetorical, left as an exercise for the reader in determining the validity
of your statements.

Spam: it's not just for breakfast anymore....

Dean Robb
PC-Easy
On-site computer services
(757) 495-EASY [3279]

Eric Eden, Internic:
In this case we removed the host and notified the contact of the
host because it is not currently serving any domain names or
networks in our database.

[Not because there was anything "false" about it. It is still served up by
Tonic]

*Sigh*. The host at InterNIC was registered with a false IP address and a
false DNS provider. The Tonic entry was correct. How hard is this to
understand?

Dean Robb:
Most excellent. Now, what would you have done if it was Dirtbag.com that
had provided the false information?

I have to question why people intentionally supply false information.
Perhaps to avoid harassment from radical and misguided people? I have to
presume in this case that Mr. Robb considers himself the sole judge of
appropriateness of the entity. Given that youwant.to was perfectly legit,
except for some cruftiness, I don't think we can really trust his judgement
on such matters.

1. Fortunately, no one is asking you to trust my judgement. Not, of
course, that yours is provably better since you provably don't know what
you're talking about.

2. I do not consider myself sole judge of anything (except my behavior and
[temporarily] that of my infant son. I point you to RFCs 2050, 1032, 1033,
920, 1173 and 1174 (that I know of offhand) that require current and
correct NIC and WhoIs information from the registrant/owner of a domain. I
quote in whole 2 paragraphs from the current NSI Registration Agreement:

K. Warranty. Registrant warrants by submitting this Registration
Agreement that, to the best of Registrant's knowledge and belief, the
information submitted herein is true and correct, and that any future
changes to this information will be provided to NSI in a timely manner
according to the domain name modification procedures in place at that
time. Breach of this warranty will constitute a material breach.

L. Revocation. Registrant agrees that NSI may delete a
Registrant's domain name if this Registration Agreement, or subsequent
modification(s) thereto, contains false or misleading information, or
conceals or omits any information NSI would likely consider material
to its decision to approve this Registration Agreement.

So you see, it's not ME being a judge, it's following the rules of the
Internet and InterNIC. Really, you should be more familiar with the RFCs
and InterNIC guidelines if you run an ISP and consult. It helps to know
the material you're consulting about.

This brings up an issue with whois databases that is relevant to nanog:
Who should have access to whois contact information and its misuse.

A valid point of discussion. Be sure to include the members of the IS,
IETF, et al that made that provision part of the Internet Standards RFCs.

Perhaps we need to have a way to authenticate and limit who can get phone
numbers and email addresses from the whois database, in order to prevent
the kind of harassment and abuse apparently exercised by Mr. Robb.

Ah, now we see a slanderous comment! Prove I have engaged in any form of
harassment or abuse, sir. Otherwise, we can only conclude that you are a
fool, and a liar, and an "anti-anti-spammer terrorist". Welcome to ad
hominem.

There is a reasonable debate that can be held regarding privacy issues and
directory services. There are a couple of RFCs (whose numbers I don't have
at hand) on this issue. I'll not respond to Mr. Anderson on the matter
though...he hurt my feewings.

Spam: it's not just for breakfast anymore....

Dean Robb
PC-Easy
On-site computer services
(757) 495-EASY [3279]

Correct. The stated purpose of WhoIs (in all it's guises) is to provide
contact information for a domain. This information is supposed to be
publicly available to provide a way for a user or other sysadmin to contact
the domain owner/technical people. Thus, if you have a misconfigured mail
server that's bouncing all "postmaster" mail, I can email your tech or zone
contact to let them know, or place a phone call, or whatever. That's why
several RFCs require correct contact data to be in WhoIs.

The misuse aspect has come about because spammers (primarily) have bots
that will harvest all the addresses in WhoIs and send them their drivel.

Many people, because of this abuse, want to NOT have their email address
listed in WhoIs...but that defeats the good purpose of the database.
Probably the best way to handle this right now is to use a role account in
the registration and put spam filters on that account. It's important to
read mail to that account, though, because in the trash could easily be
something important.

So far, MOST (but not all) of those (that I've seen) arguing vehemently for
complete anonymity in WhoIs and/or having no valid contact data are those
persons trying to hide their identity because they are engaging in Net
abuse of one form or another. There are a few, though, that are just
privacy fanatics with no special agenda.

Spam: it's not just for breakfast anymore....

Dean Robb
PC-Easy
On-site computer services
(757) 495-EASY [3279]

I'll note here, (being the smut monger that I am :slight_smile: that several of
the "live-cam" site operators, the JenniCam, for example, have whois
information that is _useful_, but might be accused of being
"misleading" for good reasons which I ought not have to explain.

On the net, no one knows where you live.

Cheers,
-- jr 'unless you put your ICBM address in your sig' a

Round one to Robb, on a TKO.

Let's not have a round two, ok, gentlemen?

Cheers,
-- jra

Having once again proved that you cannot underestimate the power of human
stupidity, I store my gloves. I like *intelligent* discourse, not
discombubulated ramblings.

Spam: it's not just for breakfast anymore....

Dean Robb
PC-Easy
On-site computer services
(757) 495-EASY [3279]

Hey, Dean!

You misspelled "discombobulated".

Cheers,
-- jra

I concede that I have been outdone by Professor Robb. I am unable to
comprehend his logic, and my mail spool isn't large enough to contain his
rambling tirades. I would respond point by insensible point to his mail,
but I have limited time.

Dr Robb (aka God) has the amazing ability to detect incorrect host records
from his planet by psychic intuition, and doesn't need to go through the
tedium of actually checking with people who are authoritative for a domain
or IP, like the rest of us, since he is authoritative. This is not
something to be wasted or trifled with. Indeed, one must demand that
Internic immediately delete the offending record, and then notify the
contacts. In retrospect, I can see that simply sending mail to contacts at
host.net and youwant.to is a waste of time for someone who is
authoritative. I apologize for not realizing this sooner.

He is also right that the only explanation is that someone was out to
hijack perhaps.youwant.to. using a newly discovered technique of adding
host records to another registry. Previously, DNS experts thought that
this would have no effect, and was therefore on the same level as harmless
cruft. The fact that youwant.to did not actually appear to be effectively
hijacked was part of the clever disguise of the crime. I must admit I did
not have the intellect to see through this deception. I am very grateful to
Dr. Robb for setting me straight.

Also quite clearly, there is absolutely no way this could have been done
accidentally. I don't know what I was thinking when I thought it might be
possible that host.net just cut the wrong information into one of their own
host records. Luckily, we were saved by Professor Robbs fast action and
harsh words, in spite of ourselves.

I don't know how we can thank him. We should do something since he says he
has no time for himself. (Selfless too!)

Perhaps we could give him his own Nic contact handle, so he can register
his own domain and host records. Or at least so the Internic can more
quickly and efficiently implement his pronouncements on incorrect
registration information.

Also, why don't we just have the various registries get Dean Robb to
approve any changes to the database? This would save tremendous effort.

    --Dean

P.S. For a while, I was somewhat alarmed by the prospect of an angry
nutcase, but I am now persuaded that Dean Robb is in fact harmless.

<sigh>

Dean, Dean... and I had such high hopes for you.

His assertion, that the interNIC ought to follow it's own published
procedures and follow up on reports of bogus data, attempting
correction, and in extremis, deleting such records, seems to stand on
it's own.

It's also apparent from others' comments that they do not, which does
not surprise me at all, given _my_ past experiences with the InterNIC.

Have A Nice Day, Dean.

Cheers,
-- jra

Can we put this to rest.

TIA

His assertion, that the interNIC ought to follow it's own published
procedures and follow up on reports of bogus data, attempting
correction, and in extremis, deleting such records, seems to stand on
it's own.

That they should follow their procedures is obvious, and not in dispute.

But they didn't "follow up" in this case, or follow their procedures
either. After arguing with Mr. Robb, they Eric pragmatically decided that
no one was actually using the record and they would delete it.

Eric (from Internic) had no information other than Mr. Robbs blind and loud
assertions that the record was incorrect. For all Eric or anyone knows,
youwant.to is about to be legitimately rehosted to host.net. The only
person to offer contrary evidence is Dal who says he knows the owner of the
domain, but he isn't a listed contact either. Furthermore, he appears to
only have sent mail to Nanog, and not to Eric, at least, so far as I can
tell.

So Internic deleted a record on the word of someone who has no direct
connection with either the IP address or the domain name. Not only that,
the person they trusted doesn't even have a contact handle, and is not a
contact for any domain or host record.

I'm surprised you didn't follow that.

    --Dean