Jump to content

.co whois url


Recommended Posts

  • Replies 53
  • Created
  • Last Reply

Top Posters In This Topic

I've already added this following code, but I still have the error message below :

 

An Error Occured

Domain Registration Error - Invalid domainName For Given ContactType

 

Any one have the same problem ?

 

Just to add, .CO domain name require domain pre-configuration.

 

Add the following code to the /billing/includes/additionaldomainfields.php file.

 

 

## .CO DOMAIN REQUIREMENTS ##



$additionaldomainfields[".co"][] = array(

"Name" => "Registrant Contact",

"Type" => "text",

"Size" => "30",

"Default" => "",

"Required" => true,

);

Link to comment
Share on other sites

You shouldn't need to add any additional fields - the Emon module will pull these down for any domains that require preconfiguration. The issue we're havign is specifically because the whois database that is used to check domain availability is not accurate.

Link to comment
Share on other sites

You shouldn't need to add any additional fields - the Emon module will pull these down for any domains that require preconfiguration. The issue we're havign is specifically because the whois database that is used to check domain availability is not accurate.

 

Are you using enom or resellerclub (netearthone etc...) ?

Link to comment
Share on other sites

It would be nice if Enom would provide some feedback on how they're doing this as both enom's whois server and the .co server are reporting many domains as available which are not. We've withdrawn .co's due to this as it's causing a huge mess with customers thinking they've got domains when they haven't.

Link to comment
Share on other sites

Turns out ResellerClub (and therefore NetEarthOne/Stargate etc) have added a specific API command required to register a .co domain and as such the WHMCS needs to be updated. This will be included in 4.3.

 

Can you please tell me the API command resellerclub/netearthone uses .CO domain names?

Link to comment
Share on other sites

  • WHMCS Support Manager
How does this work around the initial whois lookups then as the domains will still show as available and allow a customer to order them. The registrar module only comes into play when the order is paid for and submitted for registration.

See the start of the thread for the whois servers you need to add to check the availability of .co domains.

 

V4.3 is likely to be released next month.

Link to comment
Share on other sites

That doesn't actually solve the issue - there are many domains currently in the auction phase still or have been reserved. The whois database still shows these as being available, hence the issue with customers trying to order domains and then finding that they are not actually available once they have paid for them.

Link to comment
Share on other sites

  • WHMCS Support Manager

There isn't a whole lot we can do if the whois server reports domains are available when they are infact reserved. That's an issue to be taken up with the .co registry and presumably many others are experiencing the same problem.

Link to comment
Share on other sites

That's why I questioned your comment before, as there will still be a serious issue with registering .co domains until the registry get their act together and run an accurate whois database.

 

The issue is prevalent in whmcs configured to register .co domains, but doesnot occur if we use the enom or rc interface to register a .co domain. I think we still donot have a foolproof whois server or reservation checking method in whmcs for .co domains.

Link to comment
Share on other sites

The issue is prevalent in whmcs configured to register .co domains, but doesnot occur if we use the enom or rc interface to register a .co domain. I think we still donot have a foolproof whois server or reservation checking method in whmcs for .co domains.

 

They must be using a different whois server?

Hence why I asked if there was some way of using the whois from the relevant registrar via the API

 

- Vincent

Link to comment
Share on other sites

This would rquire a redesign of the whois lookup system in WHMCS though even if this is available via the API. Hopefulyl once the auction phase is complete it work wor as per any other registry then as long as the whosi database is accurate.

Link to comment
Share on other sites

We have the same issue with registering .co.nz domain names with Resellerclub - Domain Registration Error - Invalid domainName For Given ContactType and have submitted a ticket.

 

Editing additionaldomainfields.php doesn't fix the issue.

 

Here is the link to the RC API guide

 

http://manage.resellerclub.com/kb/servlet/KBServlet/faq418.html

Link to comment
Share on other sites

  • 2 weeks later...

Hi,

we have WHMCS panel installed and we modified these files:

 

/includes/whoisservers.php

we added:

.co|whois.nic.co|Not found

.net.co|whois.nic.co|Not found

.com.co|whois.nic.co|Not found

.nom.co|whois.nic.co|Not found

 

and also we added the below PHP code to /includes/additionaldomainfields.php

## .CO DOMAIN REQUIREMENTS ##

 

 

 

$additionaldomainfields[".co"][] = array(

 

"Name" => "Registrant Contact",

 

"Type" => "text",

 

"Size" => "30",

 

"Default" => "",

 

"Required" => true,

 

);

 

we can check domain availabality in whois page correctly , but when we try to register a .co domain we get this error:

"An Error Occured

Domain Registration Error - Invalid domainName For Given ContactType"

 

would you please help us!?

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    • No registered users viewing this page.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated