Some TLDs Unavailable

[Craft]

Hello,

There are some TLDs are unavailable when I search for them although the domains are available on the Lookup provider.

.us and .co are always unavailable.

Kindly find the attached screenshots.

[brian!]

On 11/09/2018 at 22:43, Craft said:

There are some TLDs are unavailable when I search for them although the domains are available on the Lookup provider.

have you added pricing for these TLDs in Domain Pricing?

[Craft]

 

5 hours ago, brian! said:

have you added pricing for these TLDs in Domain Pricing?

Yes offcourse.

[brian!]

On 13/09/2018 at 23:14, Craft said:

Yes of course.

you'd be surprised by how many users don't! 🙄

when you do a whois lookup in the admin area for a .us or .co domain, are there any errors?

[Craft]

10 hours ago, brian! said:

you'd be surprised by how many users don't! 🙄

when you do a whois lookup in the admin area for a .us or .co domain, are there any errors?

 

Lets fix .co first

When I tried to register .co domain from my whmcs admin, it succeeded.

[WHMCS ChrisD]

Just checking, you are using the default Six Theme & Standard Cart and you haven't removed or edited the whois lookup files /resources/domains/dist.whois.json. 

[Craft]

1 hour ago, WHMCS ChrisD said:

Just checking, you are using the default Six Theme & Standard Cart and you haven't removed or edited the whois lookup files /resources/domains/dist.whois.json. 

I'm using the standard cart and the default theme yes .. and I never edited this json file before.

 

[brian!]

13 hours ago, Craft said:

Lets fix .co first

I would imagine the solution to one will be the solution to both.

13 hours ago, Craft said:

When I tried to register .co domain from my whmcs admin, it succeeded.

did you do a whois lookup from the admin area?

in fact, you should do it twice - once for a domain that you know doesn't exist and one that does... and that should tell you if it's giving an accurate response...

[Craft]

12 hours ago, brian! said:

I would imagine the solution to one will be the solution to both.

did you do a whois lookup from the admin area?

in fact, you should do it twice - once for a domain that you know doesn't exist and one that does... and that should tell you if it's giving an accurate response...

 

Sorry, I didn't try WHOIS Lookup before.

I just tried now and searched for both TLDs, I tried twice for a domain doesn't exist and the other that does. Both trials gave me this error (domain is already registered)

[brian!]

then I assume you are not using the latest v7.6.1 release as both those domains should work correctly in there...

if you aren't, then you'll need to create a whois.json file in /resources/domains (don't edit dist.whois.json) and paste the following into it.

https://docs.whmcs.com/WHOIS_Servers

[
    {
        "extensions": ".co,.net.co,.com.co,.nom.co",
        "uri": "socket://whois.nic.co",
        "available": "No Data Found"
    },
	{
        "extensions": ".us",
        "uri": "socket://whois.nic.us",
        "available": "No Data Found"
    }
]

hopefully, whois lookups in the admin area will then work, and then you can check the cart to see if the searches are correct there too.

[Craft]

16 hours ago, brian! said:

then I assume you are not using the latest v7.6.1 release as both those domains should work correctly in there...

if you aren't, then you'll need to create a whois.json file in /resources/domains (don't edit dist.whois.json) and paste the following into it.

https://docs.whmcs.com/WHOIS_Servers

[
    {
        "extensions": ".co,.net.co,.com.co,.nom.co",
        "uri": "socket://whois.nic.co",
        "available": "No Data Found"
    },
	{
        "extensions": ".us",
        "uri": "socket://whois.nic.us",
        "available": "No Data Found"
    }
]

hopefully, whois lookups in the admin area will then work, and then you can check the cart to see if the searches are correct there too.

 

Yes you are correct, I'm still using version 7.3.0

Ok, I created the file and it worked fine from admin area and cart.

Then I delete the file and edited the original file "dist.whois.json",  I integrated the same code with it and it works fine too.

Thanks for your help :)

[WHMCS ChrisD]

@Craft Is there anything holding you on 7.3.0?  Thats quite an old version now

[Craft]

6 hours ago, WHMCS ChrisD said:

@Craft Is there anything holding you on 7.3.0?  Thats quite an old version now

nope, i will upgrade to the latest version soon :)

[brian!]

11 hours ago, Craft said:

Ok, I created the file and it worked fine from admin area and cart.

so far so good....

11 hours ago, Craft said:

Then I delete the file and edited the original file "dist.whois.json",  I integrated the same code with it and it works fine too.

it will do, but the reason I told you not to edit that file is because WHMCS will overwrite it during an update - now in practice, that won't matter for you at this stage.. but it's not a good habit to get into doing.

btw - if you can download the latest v7.6.1 release, there's no reason why you couldn't just upload the dist.whois.json from that zip and overwrite your current file... these files are version-dependent, so that file should work on any v7 WHMCS version and I bet there will be other entries in your dist.whois.json file that will be out of date too.

6 hours ago, WHMCS ChrisD said:

Is there anything holding you on 7.3.0?  Thats quite an old version now

it's not even a year old - come on Chris, you don't work for Support any more and no longer need to peddle that myth that the best version is always the latest version... I can think of any number of valid reasons why someone shouldn't update and one of them may apply to the OP's situation.

as long as they're using the v7.3.1 security release from July 2018, I don't see this as being a big issue.

[Craft]

3 minutes ago, brian! said:

so far so good....

it will do, but the reason I told you not to edit that file is because WHMCS will overwrite it during an update - now in practice, that won't matter for you at this stage.. but it's not a good habit to get into doing.

btw - if you can download the latest v7.6.1 release, there's no reason why you couldn't just upload the dist.whois.json from that zip and overwrite your current file... these files are version-dependent, so that file should work on any v7 WHMCS version and I bet there will be other entries in your dist.whois.json file that will be out of date too.

it's not even a year old - come on Chris, you don't work for Support any more and no longer need to peddle that myth that the best version is always the latest version... I can think of any number of valid reasons why someone shouldn't update and one of them may apply to the OP's situation.

as long as they're using the v7.3.1 security release from July 2018, I don't see this as being a big issue.

 

Ok, I understood everything you said.

I will upgrade to the latest version and I know that I shouldn't edit any original whmcs file because any new version is always overwrite it.

Thanks for your help :)