Dig gives ;; connection timed out; no servers could be reached

[Warren Kumari]

On Oct 3, 2013, at 12:47 AM, Kevin Oberman <rkoberman at gmail.com> wrote:

> On Wed, Oct 2, 2013 at 9:18 PM, Balanagaraju Munukutla <9balan at sg.ibm.com> wrote:
> 
> Hi 
> 
> Any one could help on the error below. 
> 
> 
> [andrew at oc8163211842 ~] $ dig @xxxx.com abcd.com.sg mx 
>  
> ; <<>> DiG 9.3.6-P1-RedHat-9.3.6-16.P1.el5 <<>> @xxxxx.com abcd.com.sg mx
> ; (1 server found)
> ;; global options:  printcmd
> ;; connection timed out; no servers could be reached 
> 
> [andrew at oc8163211842 ~]$ dig @xxxx.com abcd.com.sg mx 
>  
> ; <<>> DiG 9.3.6-P1-RedHat-9.3.6-16.P1.el5 <<>> @xxxxx.com abcd.com.sg mx
> ; (1 server found)
> ;; global options:  printcmd
> ;; connection timed out; no servers could be reached 
> --------------------------- 
>  
> Thanks & Regards 
> Nagaraj
> 
> This message is virtually content free. You basically said "Something in DNS failed at a very basic level, but I will remove any information that might provide even a slight clue to determine why." You hide the query and the server. All that can really be said is that your client failed to get a response from the specified server. 

Unless, maybe, he did and doesn't know how to use dig?

wkumari$ dig +norec +nocomment +nostats MX abcd.com.sg @xxxx.com
; <<>> DiG 9.8.5-P1 <<>> +norec +nocomment +nostats MX abcd.com.sg @xxxx.com
;; global options: +cmd
;; connection timed out; no servers could be reached

OK, fair enough, xxxx.com is not a name server, but: 

wkumari$ dig +norec +nocomment +nostats NS xxxx.com
; <<>> DiG 9.8.5-P1 <<>> +norec +nocomment +nostats NS xxxx.com
;; global options: +cmd
;xxxx.com.			IN	NS
xxxx.com.		3348	IN	NS	dns4.name-services.com.
xxxx.com.		3348	IN	NS	dns2.name-services.com.
xxxx.com.		3348	IN	NS	dns1.name-services.com.
xxxx.com.		3348	IN	NS	dns3.name-services.com.
xxxx.com.		3348	IN	NS	dns5.name-services.com.

; <<>> DiG 9.8.5-P1 <<>> +norec +nocomment +nostats MX abcd.com.sg @dns1.name-services.com.
;; global options: +cmd
;abcd.com.sg.			IN	MX
abcd.com.sg.		3600	IN	MX	10 p.nsm.ctmail.com.

<runs away, giggling like a maniac…>
W

> 
> Is the specified system even running DNS? Is a firewall blocking the query? The response? Is the server yours or someone else's? Is routing allowing bi-directional communication? Is these an outage that is blocking communication? The list of possibilities just goes on and on.
> 
> If you want help, you have to tell us something more than that it failed.
> -- 
> R. Kevin Oberman, Network Engineer
> E-mail: rkoberman at gmail.com
> _______________________________________________
> Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list
> 
> bind-users mailing list
> bind-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users

--
Don't be impressed with unintelligible stuff said condescendingly.
    -- Radia Perlman.