Thanks, I went ahead and added a error out. In case anyone else decides to do this, here is one. Just put it after the "my" variables are defined
in the sub lookup subroutine...
 
    if ($domain =~ /\.name$/) {
 # We don't YET want to handle .name registrations, since they are in pre-reg.
 error_out("<br>Sorry .name lookups are NOT allowed.<br><br>They are in Pre-Registrations, so if you want a pre-registration for .name click <a href="\"https://www.firstratehosting.com/register/cgi-bin/name.cgi\">here</a>.");
 exit;
    }
 
Just Customize the error out message
 
 
Thanks
Richard.
http://www.firstratehosting.com "Your Host With the Most!"
http://register.firstratehosting.com/cgi-bin/reg_system.cgi Register your Domain with prices starting at ONLY $8.50 Per Year!
https://www.firstratehosting.com/register/cgi-bin/name.cgi Pre-Register your .name domain TODAY!
----- Original Message -----
Sent: Friday, February 08, 2002 12:59 PM
Subject: RE: .name question...

Write a quick reg_exp from that form to disallow anything.name?
 
Or run two OpenSRS.conf - one for the .name pre-reg script, one for your regular stuff - since .name pre-reg is temporary, you don't need a super fancy setup...  You can ecen share the same libraries and opensrs directory
 

Charles Daminato
OpenSRS Product Manager
Tucows Inc. - [EMAIL PROTECTED]

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of POWERHOUSE
Sent: February 8, 2002 1:47 PM
To: [EMAIL PROTECTED]
Subject: .name question...

Uhm, I just thought of something. With the reg_system.cgi script,
and the reg_system.name.cgi script, they both use the OpenSRS.conf file.
and If the OPENSRS_TLDS_REGEX => has .name in it, then what is to keep people from using
the reg_system.cgi script to try to register .name domains??
 
I tried it, and it did pull up the domain, as "Available".
How do we stop that from being avialable in the reg_system.cgi, but still available for the .name script?
 
Any SIMPLE command to add?
 
Thanks
Richard.
 

Reply via email to