Connection reset/time out about whois HOT 4 CLOSED

Hello lamnk,
not really. The cause of the error is a temporary unavailability of the WHOIS server.

I'm experiencing the same problem quite often in my application.
The problem is noticeable especially with .net and .com domains because the WHOIS request involves multiple WHOIS queries, due to the nature of the Verisign WHOIS architecture.

Usually, this error is caused by the final endpoint, not by Verisign. I'm trying to isolate the problem and understand if it makes sense to return the partial response anyway in case the second WHOIS query doesn't complete successfully.

from whois.

Thank weppos, good to know. I am looking forward to updates.

from whois.

I ran into this issue as well, just like described above, the issue only happens sometimes. .com domains that I have registered through Dreamhost will occasionally fail if their server refuses the request. clickpickle.com and magnificentmurderbeasts.com are two examples of this.

It looks like the unix whois utility takes this possibility into account and returns the Verisign response without the referral WHOIS server's response.

I forked and was working on a fix. The issue is testing. The referral servers are responding again and I don't have domains to test against at the moment.

Thoughts?

from whois.

I forked and was working on a fix. The issue is testing. The referral servers are responding again and I don't have domains to test against at the moment.

You should use unit tests for this feature.

My idea was to implement this feature as a Whois::Client option. The user should be able to pass an option to allow partial responses. In case the feature is enabled (disabled by default), the system will return the partial response. Otherwise, a Whois::IncompleteResponse < ServerError error is raised.

from whois.