Hi,

I just noticed that there is _a lot_ of contact information attached to each
domain registration.

Each domain has 56 fields of just contact and registrant information: the
owner, admin contact, tech contact, and billing contact each have 14 fields
(first-name, last-name, org-name, address1, address2, address3, city, state,
postal-code, country, phone, fax, email, url).

I'm working on an interface that would present all of this to the user on one
big edit page. It's kind of overwhelming all on one page.

Out of curiosity, I looked at the whois information on my domain, and I saw a
subset of the full information which is much more palatable:

}} Registrant:
}}  DRH Internet Inc.
}}  3777 Plum Hill Ct.
}}  Ellicott City, MD 21042
}}  US
}}
}}  Domain Name: DRH.NET
}}
}}  Administrative Contact:
}}     Harris, David  [EMAIL PROTECTED]
}}     410-461-5316
}}
}}  Technical Contact:
}}     Harris, David  [EMAIL PROTECTED]
}}     410 461 5316
}}
}}  Billing Contact:
}}     Harris, David  [EMAIL PROTECTED]
}}     410-461-5316

Why do we need to have addresses stored for the administrative and technical
contacts? I understand that the billing contact needs an address (at least for
those who don't have their own billing database between the customer and
OpenSRS) and it is nice to keep the contacts consistent, so I'm not suggesting
that the codebase be changed.

What I want to know is this: Can I be guaranteed that the fields (address1,
address2, address3, city, state, postal-code, country) for the administrative
and technical contact will never be shown through whois, and therefore I can
feed OpenSRS dummy information?

I mean how many people want to enter the same address twice between the
administrative contact and owner data? How many people really look up the
physical address of their web hosting company when registering their domain? Is
anyone ever going to need the physical address of the web hosting company to be
in whois? I'd think that name, e-mail, phone number, fax number, and url would
be enough.

Perhaps it's even possible to make these fields not-required anymore. I'd love
that, as I could avoid sending dummy info down the pipe.

Thanks.

David Harris
President, DRH Internet Inc.
[EMAIL PROTECTED]
http://www.drh.net/


Reply via email to