Name Toolkit

FREEMIUM
By nametoolkit | Updated 19일 전 | Business
Popularity

0.2 / 10

Latency

8ms

Service Level

0%

Health Check

N/A

Back to All Discussions

.NL check not working (Errno::EIO at /whois/domain.nl)

Rapid account: Vincentvdaal
vincentvdaal
10년 전

Seems there is something wrong with checking the .NL extension

Errno::EIO at /whois/nu.nl
Input/output error - <STDERR>
file: base.rb location: write line: 1113
BACKTRACE
(expand)

JUMP TO: GET POST COOKIES ENV
/usr/lib/ruby/1.9.1/webrick/httpserver.rb in service
si.service(req, res)
/usr/lib/ruby/1.9.1/webrick/httpserver.rb in run
server.service(req, res)
/usr/lib/ruby/1.9.1/webrick/server.rb in block in start_thread
block ? block.call(sock) : run(sock)
GET
No GET data.

POST
No POST data.

COOKIES
No cookie data.

Rack ENV
Variable Value
GATEWAY_INTERFACE
CGI/1.1
HTTP_ACCEPT
/
HTTP_CONNECTION
Keep-Alive
HTTP_HOST
api.nametoolkit.com
HTTP_USER_AGENT
unirest-php/1.0
HTTP_VERSION
HTTP/1.1
HTTP_X_FORWARDED_FOR
37.16.0.35, 23.23.103.218, 23.23.103.218
HTTP_X_FORWARDED_HOST
api.nametoolkit.com
HTTP_X_FORWARDED_PORT
443
HTTP_X_FORWARDED_PROTO
https
HTTP_X_FORWARDED_SERVER
api.nametoolkit.com
HTTP_X_MASHAPE_PROXY_RESPONSE
false
HTTP_X_MASHAPE_PROXY_SECRET
hcyPe811RpvXirB5LPJp0NFddZlfmr
HTTP_X_MASHAPE_SUBSCRIPTION
FREE
HTTP_X_MASHAPE_USER
vincentvdaal
HTTP_X_MASHAPE_VERSION
3.0.2
PATH_INFO
/whois/nu.nl
QUERY_STRING
REMOTE_ADDR
127.0.0.1
REMOTE_HOST
localhost
REQUEST_METHOD
GET
REQUEST_PATH
/whois/nu.nl
REQUEST_URI
https://api.nametoolkit.com/whois/nu.nl
SCRIPT_NAME
SERVER_NAME
api.nametoolkit.com
SERVER_PORT
443
SERVER_PROTOCOL
HTTP/1.1
SERVER_SOFTWARE
WEBrick/1.3.1 (Ruby/1.9.3/2011-10-30)
rack.errors
#Object:0x0000000170c4b0
rack.input
#StringIO:0x007f754c1d1eb0
rack.logger
#<Logger:0x007f754c1d1780 @progname=nil, @level=1, @default_formatter=#<Logger::Formatter:0x007f754c1d16b8 @datetime_format=nil>, @formatter=nil, @logdev=#<Logger::LogDevice:0x007f754c1d1668 @shift_size=nil, @shift_age=nil, @filename=nil, @dev=#<IO:<STDERR>>, @mutex=#<Logger::LogDevice::LogDeviceMutex:0x007f754c1d15f0 @mon_owner=nil, @mon_count=0, @mon_mutex=#Mutex:0x007f754c1d15a0>>>
rack.multiprocess
false
rack.multithread
true
rack.request.cookie_hash
{}
rack.request.query_hash
{}
rack.request.query_string
rack.run_once
false
rack.url_scheme
http
rack.version
[1, 2]
sinatra.accept
[/]
sinatra.commonlogger
true
sinatra.error
#<Whois::ResponseIsThrottled: Whois::ResponseIsThrottled>
You’re seeing this error because you have enabled the show_exceptions setting.

Rapid account: Nametoolkit
nametoolkit Commented 10년 전

We just deployed a release where we are doing lookups across several servers, let us know if this is still an issue. You’ll need the latest API clients to avail of the fix, backwards-compatibility is there with the old clients for the moment.

Rapid account: Vincentvdaal
vincentvdaal Commented 10년 전

That explains why it was just working and isn’t now 😃 thanks. I’ll keep the issue open until resolved.

Rapid account: Vincentvdaal
vincentvdaal Commented 10년 전

It’s working again, must have been a temporarily bug. Closing issue.

Rapid account: Nametoolkit
nametoolkit Commented 10년 전

This is a timeout bug or occurs when the whois servers throttle us for making too many lookups we’re working on making this more robust atm and will announce when we have it.

Rapid account: Vincentvdaal
vincentvdaal Commented 10년 전

What do you exactly mean with “You’ll need the latest API clients to avail of the fix, backwards-compatibility is there with the old clients for the moment.” the sentence doesn’t make much sense, sorry 😃

Rapid account: Nametoolkit
nametoolkit Commented 10년 전

Sorry, allow me to elaborate. The v1 version of the API (not the beta one) has had some improvements made last week. To allow me to “version” the api it now has a version number in the url path “/v1/”. If you are using the REST API you could simply change the API url you’re using to be e.g. “/v1/whois?q=blah.com”, alternatively if you’re using one of the Mashape auto-generated client SDK’s for our API you can simply re-download a newer version and it will have this change in it.
If you find the beta API more useful please let us know and any other feedback you have is greatly appreciated.

Thanks,
Mark

Join in the discussion - add comment below:

Login / Signup to post new comments