Seems like they have deactivated their whois server and only allow rdap queries.
I’ll have to do a little change in the plugin to consider this.
A update of the plugin will be released for that in the next days.
The update is now published and checking .bw should work again.
Thread Starter
opqnet
(@opqnet)
Hi,
Thanks for your attention to this.
Unfortunately, checking the .bw space now returns: error
You have not setup a custom whois server for that TLD? In my tests checking works without errors.
If you enable the whois link in the settings, you should be able to see the error message in the details window.
Thread Starter
opqnet
(@opqnet)
I had previously set up the custom Whois server for the .bw space.
Find
Enter the desired TLD and check if there is an appropriate server.TLD
Results with bw:
1 TLDsbw (rdap.nic.net.bw)
See above results. However we cannot register domains with just .bw (i.e. name.bw), rather we have to register name.co.bw or name.ac.bw etc.
Testing with these produces the following:
Find
Enter the desired TLD and check if there is an appropriate server.TLD
Results with co.bw:
0 TLDs
Thread Starter
opqnet
(@opqnet)
Hi,
Also, got the following response from the IT support:
Good day,
The port 43 WHOIS is depreciated / retired internet standard. Kindly use EPP to check availability and register / edit. See below the EPP commands,
https://www.rfc-editor.org/rfc/rfc5730.html#page-23
I have added .co.bw as a custom whois server and it seems to work properly.
My settings:
– TLD: co.bw
– Whois server: rdap.nic.net.bw
– Status free: no object found
