Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Getting Whois::ParserError for .be-domains. #218

Closed
SebastianJ opened this Issue Apr 3, 2013 · 5 comments

Comments

Projects
None yet
2 participants

Getting the following error when trying to check e.g. 21century.be:

Unable to parse status. Please report the issue at http://github.com/weppos/whois/issues

@ghost ghost assigned weppos Apr 3, 2013

Owner

weppos commented Apr 3, 2013

What version of the library are you using? It works great for me.

irb -rubygems -I lib -r whois.rb
1.9.3-p327 :001 > r = Whois.query "21century.be"
 => "% .be Whois Server 5.0\r\n%\r\n% The WHOIS service offered by DNS.be and the access to the records in the DNS.be\r\n% WHOIS database are provided for information purposes only. It allows\r\n% persons to check whether a specific domain name is still available or not\r\n% and to obtain information related to the registration records of\r\n% existing domain names.\r\n%\r\n% DNS.be cannot, under any circumstances, be held liable where the stored\r\n% information would prove to be incomplete or inaccurate in any sense.\r\n%\r\n% By submitting a query you agree not to use the information made available\r\n% to:\r\n%   - allow, enable or otherwise support the transmission of unsolicited,\r\n%     commercial advertising or other solicitations whether via email or otherwise;\r\n%   - target advertising in any possible way;\r\n%   - to cause nuisance in any possible way to the domain name holders by sending \r\n%     messages to them (whether by automated, electronic processes capable of\r\n%     enabling high volumes or other possible means).\r\n% \r\n% Without prejudice to the above, it is explicitly forbidden to extract, copy\r\n% and/or use or re-utilise in any form and by any means (electronically or\r\n% not) the whole or a quantitatively or qualitatively substantial part\r\n% of the contents of the WHOIS database without prior and explicit permission\r\n% by DNS.be, nor in any attempt thereof, to apply automated, electronic\r\n% processes to DNS.be (or its systems).\r\n%\r\n% You agree that any reproduction and/or transmission of data for commercial\r\n% purposes will always be considered as the extraction of a substantial\r\n% part of the content of the WHOIS database.\r\n%\r\n% By submitting the query you agree to abide by this policy and accept that\r\n% DNS.be can take measures to limit the use of its whois services in order to\r\n% protect the privacy of its registrants or the integrity of the database.\r\n%\r\n\r\nDomain:\t21century.be\r\nStatus:\tNOT AVAILABLE\r\nRegistered:\tThu Dec 6 2012\r\n\r\nRegistrant:\r\n\tNot shown, please visit www.dns.be for webbased whois.\r\n\r\nRegistrar Technical Contacts:\r\n\tName:\tNetworking.be\r\n\tOrganisation:\tNetworking.be\r\n\tLanguage:\tnl\r\n\tPhone:\t+32.0\r\n\tFax:\t+32.0\r\n\tEmail:\tinfo@networking.be\r\n\r\n\r\nRegistrar:\r\n\tName:\t Hantai b.v.b.a.\r\n\tWebsite: domein.hantai.be\r\n\r\nNameservers:\r\n\tns2.sedoparking.com\r\n\tns1.sedoparking.com\r\n\r\nKeys:\r\n\r\nPlease visit www.dns.be for more info.\r\n" 
1.9.3-p327 :002 > r.status
 => :registered 

Hey!

Sorry for forgetting to supply the version. I'm using the version straight from git, in my Gemfile:

gem "whois", :git => 'git://github.com/weppos/whois.git'

Using rails console:
1.9.3-p392 > r = Whois.query "21century.be"
=> "% .be Whois Server 5.0\r\n%\r\n% The WHOIS service offered by DNS.be and the access to the records in the DNS.be\r\n% WHOIS database are provided for information purposes only. It allows\r\n% persons to check whether a specific domain name is still available or not\r\n% and to obtain information related to the registration records of\r\n% existing domain names.\r\n%\r\n% DNS.be cannot, under any circumstances, be held liable where the stored\r\n% information would prove to be incomplete or inaccurate in any sense.\r\n%\r\n% By submitting a query you agree not to use the information made available\r\n% to:\r\n% - allow, enable or otherwise support the transmission of unsolicited,\r\n% commercial advertising or other solicitations whether via email or otherwise;\r\n% - target advertising in any possible way;\r\n% - to cause nuisance in any possible way to the domain name holders by sending \r\n% messages to them (whether by automated, electronic processes capable of\r\n% enabling high volumes or other possible means).\r\n% \r\n% Without prejudice to the above, it is explicitly forbidden to extract, copy\r\n% and/or use or re-utilise in any form and by any means (electronically or\r\n% not) the whole or a quantitatively or qualitatively substantial part\r\n% of the contents of the WHOIS database without prior and explicit permission\r\n% by DNS.be, nor in any attempt thereof, to apply automated, electronic\r\n% processes to DNS.be (or its systems).\r\n%\r\n% You agree that any reproduction and/or transmission of data for commercial\r\n% purposes will always be considered as the extraction of a substantial\r\n% part of the content of the WHOIS database.\r\n%\r\n% By submitting the query you agree to abide by this policy and accept that\r\n% DNS.be can take measures to limit the use of its whois services in order to\r\n% protect the privacy of its registrants or the integrity of the database.\r\n%\r\n 21century.be\r\n-3: IP address blocked\r\n"

1.9.3-p392 > r.status
Whois::ParserError: Unable to parse status. Please report the issue at http://github.com/weppos/whois/issues

It says "IP address blocked" in the end, it might just be that I've sent too many requests too fast...

Do you want me to close the issue?

Owner

weppos commented Apr 3, 2013

IP address blocked

It looks like your IP has been throttled.

Owner

weppos commented Apr 3, 2013

As a side note, I encourage you to not link the GitHub repo directly unless strictly required. I'm planning to release more frequent updates now that the release 3.0 is out.

Yeah, I saw that as well, I wrote it in my reply as well. I'll close the issue for now :). Thanks for replying and paying attention - I appreciate the work you've put into this gem.

@SebastianJ SebastianJ closed this Apr 3, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment