Suggestion: Add contact entry to whois

Owen DeLong wrote:

We already have Admin, Tech, and Billing. Would it be possible to consider
the addition of an Abuse contact in whois?

The existing contacts serve that function. If someone at some place is
smurfing you, you don't want to talk to some secretary who is going to
stick a post-it on some manager's door about it. You want the NOC and
you want the person in the NOC who can initiate immediate investigation
and correct the problem. Well, at least I do.

Define "abuse". It comes in a lot of categories, anyway. Which category
do you think an abuse contact should be getting them for? Smurf? Flood?
Spam? Bad BGP? Hacking?

Hello All,

Owen DeLong wrote:

> We already have Admin, Tech, and Billing. Would it be possible to consider
> the addition of an Abuse contact in whois?

  Not actually a bad idea for (mail abuse) , But then the Tech
  Contact s/b able to remedy the condition by forwarding the
  info to postmaster , You have that defined for your domain
  don't you ?

The existing contacts serve that function. If someone at some place is

  I disagree with this entirely , in the last few years we have
  had a inundation of domain requests mostly from very non-technical
  individuals .

  The Administrator, isn't needed to be Technically Competent.
  The Technical Contact, -IS- , But in some cases isn't .
  The Billing Contact, isn't needed to be Technically Competent.

  And on top of this we have people whom have entered registrations
  that all of the above are to the same clueless individual .

  I would like to see an entry that can -ONLY- be entered
  by a -KNOWN- Technical Contact Associated with particular Name
  Server(s) .

smurfing you, you don't want to talk to some secretary who is going to
stick a post-it on some manager's door about it. You want the NOC and
you want the person in the NOC who can initiate immediate investigation
and correct the problem. Well, at least I do.

  How about a NOC entry ? , But then again Technical Contact s/b
  able to forward to NOC@ ....

Define "abuse". It comes in a lot of categories, anyway. Which category
do you think an abuse contact should be getting them for? Smurf? Flood?
Spam? Bad BGP? Hacking?

  Yes I agree , original poster Please define .

As stated in Internic's guidelines on the domain template, the
technical contact is "generally...the person or organization who
maintains the domain name Registrant's primary name server, resolver
software, and database files"

The DNS administrator would not automatically be the person who wants
to get all the spam, network abuse, and security incident reports. I
think the Abuse contact is a good idea.

Mark Borchers
Network Engineering Dept.
Network Two Communications Group
  "I gotta go now, yeah, I'm running out of change.
  There's a lot of things, if I could I'd rearrange."
  --U2/Achtung Baby

All of the above, except BGP issues. And the abuse/security desks at many
providers are NOT the same people who handle day-to-day tech support; I'd
like to have easy access to the phone numbers and e-mail addresses of both
the network support people and the abuse people.

> We already have Admin, Tech, and Billing. Would it be possible to

consider

> the addition of an Abuse contact in whois?

Not actually a bad idea for (mail abuse) , But then the Tech
Contact s/b able to remedy the condition by forwarding the
info to postmaster , You have that defined for your domain
don't you ?

By definition in the RFC's (remember those?) all email-related problems
should go to the postmaster. Some ISPs have set up an abuse address
specifically to handle spam problems; retaining the postmaster for more
traditional problems.

Unfortunately, we frequently find domains with a disabled or /dev/null-ed
postermaster address. Adding an abuse address would accomplish nothing.
If they don't have a working postmaster, it's not real likely they'd have a
working abuse address either.

"Small minds can only contemplate small ideas".....Unknown

Dean Robb
Owner, PC-EASY
(757) 495-EASY [3279]
On-site computer repair, upgrades and consultations
Read my game reviews/columns in SimOps on WWW.TheGamers.Net

A resource that might help is abuse.net. They'll auto-forward an abuse
problem to the correct address for a large number of ISPs.

"Small minds can only contemplate small ideas".....Unknown

Dean Robb
Owner, PC-EASY
(757) 495-EASY [3279]
On-site computer repair, upgrades and consultations
Read my game reviews/columns in SimOps on WWW.TheGamers.Net