Jump to content

New gTLDs Whois Server


nimonogi

Recommended Posts

technically, the whois entry (in v7) should be this..

 

    {
"extensions": ".xn--node",
"uri": "socket://whois.itdc.ge",
"available": "NO OBJECT FOUND!"
   },

note: if this is the last entry in your whois.json file, you won't need the last comma.

 

unfortunately, WHMCS only has partial support for IDN TLDs and even what it does do, isn't great... :roll:

 

https://forum.whmcs.com/showthread.php?107171-Domain-lookup-WHMCS-v6-x-x-and-IDN-new-gTLDs&p=442111#post442111

 

e.g if you add .გე to domain pricing and do a search in the client area, it will generate an error (even with IDN support enabled)...

 

HvnnUIT.png

 

the way around that used to be to enter the TLDs in their ASCII format... so for .გე it would be .xn--node -> then you can do a correct search...

 

IIGhczl.png

 

unfortunately, no customer will know that .გე is the same as .xn--node :roll:

 

if you were using the Modern template (or any of the older ones), you could use a Smarty plugin that would convert these IDN TLDs to their Unicode labels in the dropdown and the results...

 

f6e2tzb.png

 

and with a couple of minor template tweaks, you can then do a domain search...

 

Oj1GoAS.png

I suspect that on the invoice and elsewhere in the client area, unless modified, it would still be shown as hello2017.xn--node - also, the standard_cart template doesn't specifically use Smarty to output the domain search results, so I don't think the above Smarty plugin would work with it.

 

to be honest, it's so much hassle to add IDN TLDs as a workable option in WHMCS, that i've never really added them as I didn't think the resulting sales would justify the effort... however, if you're based in Georgia, then it might be worth doing. :?:

Link to comment
Share on other sites

Sadly I cannot use this because if the TLD is not in the chosen registrar , it will not fall back to the standard one. This means you are restricted to only and only the extensions for 1 single registrar. I have a custom extensions as well a manual registrar with my own Whois servers, not only I cannot use it but neither can anyone else that relies on the Standard Whois server for some extensions.

 

This is a bug, a very simple one to fix but still not fixed it seems:

#CORE-10906

 

I would seriously advise users to hold on before upgrading to v7. The domain features are basically completely removed and the new fancy features seems to work only half of the time. I already noticed a drop to almost no new domain registrations since I upgraded to v7, captcha not working in Firefox, Whois Lookup does not fall back to standard if TLD is not in the registrar, several pages in the templates regarding domains completely removed, etc.

 

This is hurting me financially in a big time. If someone can't properly register a domain, they will not order anything else.

Link to comment
Share on other sites

  • 2 months later...

I feel such a noob :crushed:

 

Guessing around for .shop .store and .amsterdam.

 

Ended up with something like this and its not working:

 

[

{

"extensions": ".amsterdam",

"uri": "socket://webwhois.nic.amsterdam",

"available": "Domain not found"

},

{

"extensions": ".shop",

"uri": "socket://whois.nic.shop",

"available": "Domain not found"

},

{

"extensions": ".store",

"uri": "socket://webwhois.nic.store",

"available": "Domain not found"

}

]

 

How do you all figured this * out?

 

Your help is appreciated :)

Link to comment
Share on other sites

I feel such a noob :crushed:

Guessing around for .shop .store and .amsterdam.

Ended up with something like this and its not working:

you should be using...

 

[
   {
"extensions": ".amsterdam",
"uri": "socket://whois.nic.amsterdam",
"available": "Domain Status: free"
   },
   {
"extensions": ".shop",
"uri": "socket://whois.nic.shop",
"available": "queried object does not exist"
   },
   {
"extensions": ".store",
"uri": "socket://whois.nic.store",
"available": "DOMAIN NOT FOUND"
   }
]

if you get an error with .store, then your server IP is likely being blocked by CentralNic.

Link to comment
Share on other sites

  • 2 weeks later...

Hi Everyone,

 

I would like to have an update on these:

 

- .ac|whois.nic.ac|is available for purchase

- .ac.ac|whois.nic.ac|Available

- .cr|whois.nic.cr| is not registered

- .feedback|whois.centralnic.com|DOMAIN NOT FOUND

- .fan|whois.centralnic.com|DOMAIN NOT FOUND

- .fans|whois.nic.fans|DOMAIN NOT FOUND

- .fm|whois.nic.fm|Not Registered

- .fm.br|whois.nic.br|No match for

 

Apparently these aren't working.

Edited by PAIBKK
Link to comment
Share on other sites

.by|whois.cctld.by|no entries found

 

.college|whois.nic.college|DOMAIN NOT FOUND

 

.ac.nz|whois.srs.net.nz|220 Available

.co.nz|whois.srs.net.nz|220 Available

.geek.nz|whois.srs.net.nz|220 Available

.gen.nz|whois.srs.net.nz|220 Available

.iwi.nz|whois.srs.net.nz|220 Available

.kiwi.nz|whois.srs.net.nz|220 Available

.maori.nz|whois.srs.net.nz|220 Available

.net.nz|whois.srs.net.nz|220 Available

.nz|whois.srs.net.nz|220 Available

.org.nz|whois.srs.net.nz|220 Available

.school.nz|whois.srs.net.nz|220 Available

 

.co.rs|whois.rnids.rs|%ERROR:103

.edu.rs|whois.rnids.rs|%ERROR:103

.in.rs|whois.rnids.rs|%ERROR:103

.org.rs|whois.rnids.rs|%ERROR:10

.rs|whois.rnids.rs|%ERROR:103

 

.uz|whois.cctld.uz|not found...

 

None of them are working.

Edited by PAIBKK
Link to comment
Share on other sites

.college|whois.nic.college|DOMAIN NOT FOUND

this is working correctly - but it's a CentralNic domain, which probably means that your server IP is marked as an untrusted source for making too many whois lookups (not just .college but all CentralNic domains in total) - check previous replies in this thread about contacting CentralNic support to get the restrictions removed from your server IP(s).

 

.ac.nz|whois.srs.net.nz|220 Available

again, the above New Zealand entries (all of them) are correct - if memory serves, there's a whois lookup limit with .nz domains of 50 (per day I think), so it's possible you've passed that limit and are being blocked - you'd likely need to contact dnc.org.nz to confirm that though.

 

.co.rs|whois.rnids.rs|%ERROR:103

these are wrong and should be...

.rs|whois.rnids.rs|Domain is not registered
.co.rs|whois.rnids.rs|Domain is not registered
.edu.rs|whois.rnids.rs|Domain is not registered
.in.rs|whois.rnids.rs|Domain is not registered
.org.rs|whois.rnids.rs|Domain is not registered

.uz|whois.cctld.uz|not found...

this needs to be...

.uz|whois.cctld.uz|not found in database

Link to comment
Share on other sites

Hi Fred,

 

- .inc.hk

- .int

i'll do the easier one first...

.int|whois.iana.org|query returned 0 objects

with regards to .inc.hk, I don't think there is a working port 43 whois server - there is a website whois page (http://www.whois.hk.com/), but it uses captcha so it's not usable by WHMCS.

 

I assume it's just a third-level domain like those offered by CentralNic... e.g they've registered inc.hk and are offering subdomains of it.

 

you could email them (udr.hk.com) and ask them if they have a port 43 whois server, but I doubt they will have.

Link to comment
Share on other sites

Hi Brian,

 

Thank you for the .int.

I found out that:

 

inc.hk=whois.crsnic.net

ltd.hk=whois.crsnic.net

 

Currently I am building a whois lookup for OpenCart.

It's a bit different than whmcs is using.

 

It has the servers and the tld in the same file but separate:

Example

 

[servers]

whois.donuts.co|Domain not found

whois.iana.org|query returned 0 objects

whois.nic.club|No Data Found

[/servers]

 

[tlds]

club=whois.nic.club

int=whois.iana.org

jewelry=whois.donuts.co

life=whois.donuts.co

ltd=whois.donuts.co

[/tlds]

 

It comes with its difficulties as there are verious replies on the .ua server

Example:

kharkov.ua=whois.ua

kherson.ua=whois.ua

 

The replies of the servers are:

kharkov.ua|whois.ua|:ERROR: No match record found for

kherson.ua|whois.ua|% No entries found for

However I can only direct to a server once.

Maybe you know a solution for this ???

 

 

You may visit it at:

http://paibkk.com/system/helper/whois/whois.php

 

Kind regards

Fred

Edited by PAIBKK
Link to comment
Share on other sites

Hi Fred,

 

I found out that:

 

inc.hk=whois.crsnic.net

ltd.hk=whois.crsnic.net

are you absolutely sure of that? :?:

if I take two examples of existing sites from Google - lyndsey.inc.hk and gdtl.inc.hk - both your script (and WHMCS when I add the entries) say that they're available... but they can't be, because there are active sites using them! (.whois.hk.com/ also confirms them as being registered).

 

Currently I am building a whois lookup for OpenCart.

It's a bit different than whmcs is using.

interesting - we must compare notes one day... i'll have to go through your dropdown list and see if there are any missing from mine! :)

 

i'll give you one that I can see is missing - British Universities and Colleges... you can't register them unless you are one, but you can look them up on whois!

 

.ac.uk|whois.ja.net|No such domain

 

It has the servers and the tld in the same file but separate

slightly weird! :twisted:

 

It comes with its difficulties as there are verious replies on the .ua server

Example:

kharkov.ua=whois.ua

kherson.ua=whois.ua

 

The replies of the servers are:

kharkov.ua|whois.ua|:ERROR: No match record found for

kherson.ua|whois.ua|% No entries found for

However I can only direct to a server once.

Maybe you know a solution for this ???

oh Ukraine was an absolute pain in the proverbial to work through originally with all those regional variations. :cry:

 

.kharkov.ua|whois.kh.ua|No match record found
.kherson.ua|whois.ua|No entries found

there are some that use "No match record found", others use "No entries found" or "not found"... or even "domain not in database". :mad:

Link to comment
Share on other sites

Hi Brian,

 

 

Just thinking how I will be solving this:

 

.ไทย is a Thai domain.

But this doesn't work.

 

.ไทย|whois.thnic.co.th|% No match for

 

The .ไทย is translated to: .xn--o3cw4h

But how to get this right ???

Any suggestions ?

Link to comment
Share on other sites

But how to get this right ???

Any suggestions ?

for IDN TLDs like this in WHMCS, you would use...

 

.xn--o3cw4h|whois.thnic.co.th|% No match for

and then in WHMCS front end (client/cart), you would convert .xn--o3cw4h to .ไทย - as no client is going to know what .xn--o3cw4h is.

 

in domain pricing, you would use .xn--o3cw4h - i'm not sure how Opencart would handle IDN domains though.

Link to comment
Share on other sites

  • 3 weeks later...
.ltd don't work to me

the entry in dist.whois.json is basically correct - personally, i'd use whois.nic.ltd, but that's just an alias to whois.donuts.co

 

I suspect if .ltd looks are failing for you, then you might be hitting Donut's whois lookup limits - http://www.donuts.domains/about/policies/whois - if you are, then it will be affecting other Donut TLDs too... long-term fix will be to either use one of the built-in lookup providers, or if you must use whois, then reduce the number of Donut TLDs in your alternate TLD lookups in the domain pricing setup.

 

h5QZhtD.png

Link to comment
Share on other sites

  • 2 months later...
.xyz|whois.nic.xyz|DOMAIN NOT FOUND

(there is a space after FOUND word)

and

.store|whois.nic.store|DOMAIN NOT FOUND

seems not working

any update?

the above two entries are still correct - therefore, I suspect your server IP is being blocked by CentralNic for too many whois lookups.

 

https://forum.whmcs.com/showthread.php?86494-New-gTLDs-Whois-Server&p=465103#post465103

Link to comment
Share on other sites

From few days I reveive "Unavailable" for any .biz domain I search. Any idea?

https://forum.whmcs.com/showthread.php?132687-Paypal-going-to-credit-crd-payment-page&p=529561#post529561

 

the entry in your custom whois needs updating...

    {
       "extensions": ".biz",
       "uri": "socket://whois.biz",
       "available": "No Data Found"
   },  

I think either whois.nic.biz or whois.biz will work - it's just the availability string that has changed.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • 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