Hello,

        I will figure out the way to handle this process efficiently...
One thing that I have not found any documentation on is on certain
registry requirements.  For example:  the .de registry requires a fax
number...  I noticed this when I tried submitting a test registration
and got that error.  Where can I find all of the registry requirements
for updating contacting information?  I am sure the parameters they
require and formatting might vary from one another.........

-H.A.

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, June 16, 2004 9:31 AM
To: [EMAIL PROTECTED]
Subject: Re : OpenSRS Modify Domain Contacts:
(#6932-000359-4104\3594104)

Hello,

To the best of my knowledge, if you wish to do this you can, as long as
your code can differentiate the requests. Depending on what you're
allowing to be changed in bulk you can decide if it's best to put these
type of changes in, or allow them instead on a one-by-one basis. You can
test this on the test server, horizon.opensrs.net with a group of
domains you register in the test environment. 

We also have a developers email -list called the dev-list which can be
very helpful in creating custom solutions like this.  You can search the
archives or signup at the RRC, linked below.

Hope this helps.

Frank L.
Tucows/OpenSRS Technical Support

Reseller Resource Center : https://rrc.tucows.com/
End-User Help Center :  http://helpcenter.tucows.com/


 ORIGINAL MESSAGE:
 -----------------


 From: [EMAIL PROTECTED]
 Posted At: 20:40:30.000 06/15/2004
 Posted To: [EMAIL PROTECTED] 
 Subject: OpenSRS Modify Domain Contacts: 

Hello:
            I am working on a nice backend system for my clients.  It
will allow them to make global or multiple domain changes to their
domain names.  What I am thinking about is whether or not the .US, .CA,
.INFO, registry/nexus info should be displayed in this section under
modify domain contact information.  Is it appropriate for this
information to be updated under this section?
Best Regards,
-H.A.

  


Reply via email to