Timeout in whois command
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]
linux timeout whois
asked Mar 1 '13 at 21:07
knight07
111
migrated from stackoverflow.com Mar 2 '13 at 0:36
This question came from our site for professional and enthusiast programmers.
|
show 3 more comments
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]
linux timeout whois
asked Mar 1 '13 at 21:07
knight07
111
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 dostrace -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 donestrace -v -T whois www.google.compastebin.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
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]
linux timeout whois
asked Mar 1 '13 at 21:07
knight07
111
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]
linux timeout whois
linux timeout whois
asked Mar 1 '13 at 21:07
knight07
111
asked Mar 1 '13 at 21:07
knight07
111
asked Mar 1 '13 at 21:07
knight07
111
asked Mar 1 '13 at 21:07
knight07
111
asked Mar 1 '13 at 21:07
knight07
111
111
migrated from stackoverflow.com Mar 2 '13 at 0:36
This question came from our site for professional and enthusiast programmers.
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 dostrace -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 donestrace -v -T whois www.google.compastebin.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
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 dostrace -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 donestrace -v -T whois www.google.compastebin.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
A firewall is blocking the whois service?
– ott--
Mar 1 '13 at 21:44
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
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
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
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
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
1
active
oldest
votes
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.
answered Mar 20 '13 at 0:08
Brian C
1463
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f559645%2ftimeout-in-whois-command%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
answered Mar 20 '13 at 0:08
Brian C
1463
add a comment |
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.
answered Mar 20 '13 at 0:08
Brian C
1463
add a comment |
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.
answered Mar 20 '13 at 0:08
Brian C
1463
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.
answered Mar 20 '13 at 0:08
Brian C
1463
answered Mar 20 '13 at 0:08
Brian C
1463
answered Mar 20 '13 at 0:08
Brian C
1463
answered Mar 20 '13 at 0:08
Brian C
1463
1463
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f559645%2ftimeout-in-whois-command%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
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.compastebin.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