Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Unable to figure out the problem with whois command. Whenever i give any query to whois command it gives timeout error. I also learned about jwhois command but it seems it is also getting similar problem. I am searching for this but not find anything useful. These are the error given while running the command and i also run whois on many other domain but no success. Please help!

knight07@bt:~$ whois google.com
Timeout

knight07@bt:~$ jwhois google.com
[Querying whois.verisign-grs.com]
[Unable to connect to remote host]
share|improve this question

migrated from stackoverflow.com Mar 2 '13 at 0:36

This question came from our site for professional and enthusiast programmers.

    
A firewall is blocking the whois service? –  ott-- Mar 1 '13 at 21:44
    
I don't think so, i opened port 43 for tcp and udp. But still giving the same error. –  knight07 Mar 2 '13 at 8:06
    
Can you do strace -vo whois.txt whois www.google.com (or whatever name) and put the result to pastebin.com? –  ott-- Mar 2 '13 at 13:47
    
I have done strace -v -T whois www.google.com pastebin.com/HbpibUSj and i think the error is on line 285 as it is taking almost 60 seconds and then timeout occurs. –  knight07 Mar 2 '13 at 18:54
    
Now compare that with my whois (starting at looking up whois.crsnic.net). The IP address differs, but it works for me. See pastebin.com/d9SpCbfb –  ott-- Mar 2 '13 at 20:35
show 3 more comments

1 Answer

I have the same thing happening and it's almost certainly because one of the central whois servers has blocked you for too many queries. I suspect it's Verisign's .com server that is being touchy as I can get names lik

I haven't yet found out a way to remove myself from the block list but am working on it and would appreciate hearing anything you find out!

To test this, try a whois of flabbalabbaz.info - you'll get an immediate response; then try a whois of flabbalabbaz.com or .net - you'll time out.

The most usual cause of getting blacklisted is too many queries from some sort of automated system. We have a whois script built into one of our helpdesk operators' tools, but it doesn't actually issue many requests so I'm rather disappointed they've seen fit to block us for what would only have been a relatively small number of queries.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.