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

[Balanagaraju Munukutla]

Hi

Any one could help on the error below.


[andrew@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@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

[Alan Clegg]

On Oct 3, 2013, at 12:18 AM, Balanagaraju Munukutla <9ba...@sg.ibm.com> wrote:

> [andrew@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

Looks like the connection is timing out to me. Maybe no servers could be reached.

Check the logs on the server (xxxxx.com).

Note that it times out for me as well:

----SNIP----
aclegg@ossatura ~ $ dig @xxxx.com abcd.com.sg mx

; <<>> DiG 9.9.4 <<>> @xxxx.com abcd.com.sg mx
; (1 server found)
;; global options: +cmd

;; connection timed out; no servers could be reached

----SNIP----

You haven't given us enough information to provide any reasonable answers.

AlanC
--
Alan Clegg | +1-919-355-8851 | al...@clegg.com

[Charles Swiger]

Hi--

On Oct 2, 2013, at 9:18 PM, Balanagaraju Munukutla <9ba...@sg.ibm.com> wrote:
> Any one could help on the error below.
>

> [andrew@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

Yes, it means the nameserver at xxxx.com could not be reached.

FYI, that version of dig (and presumably BIND) was deprecated back in 2009:

https://www.isc.org/downloads/software-support-policy/bind-software-status/

Regards,
--
-Chuck

PS: I get an NXDOMAIN from Google's nameserver:

% dig abcd.com.sg mx

; <<>> DiG 9.8.5-P1 <<>> abcd.com.sg mx
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 62834
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;abcd.com.sg. IN MX

;; AUTHORITY SECTION:
com.sg. 900 IN SOA ds.nic.net.sg. postmaster.nic.net.sg. 2008426338 21600 1800 2419200 900

;; Query time: 62 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Wed Oct 02 21:35:50 PDT 2013
;; MSG SIZE rcvd: 87

[Kevin Oberman]

On Wed, Oct 2, 2013 at 9:18 PM, Balanagaraju Munukutla <9ba...@sg.ibm.com> wrote:

Hi

Any one could help on the error below.


[andrew@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@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.

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: rkob...@gmail.com

[Balanagaraju Munukutla]

Hi All

To explain more on the below. We are trying to do a query on MX record for abcd.com.sg. domain to the Authoritative nameserver xxxx.com from my pc. You can see the reply as below. Done this mean that the  Authoritative nameserver xxxx.com failure or this PC where I am doing the query is blocking to communicate that local DNS server configured on it.

Please help.

Thanks & Regards
Nagaraj

Kevin Oberman <rkob...@gmail.com> Sent by: kob...@gmail.com 10/03/2013 12:47 PM

To Balanagaraju Munukutla/Singapore/AT&T/IDE@IBMSG cc bind-users <bind-...@isc.org>, Subramaniam Raju <subr...@in.ibm.com> Subject Re: Dig gives ;; connection timed out; no servers could be reached

[Steven Carr]

As others have already commented, it could mean either, there isn't enough information provided to try to identify where the fault lies.

Are these systems accessible from the Internet? if so then please provide the correct names so we can also run tests from our locations to see if we get the same results.

If you can't provide this information then you are on your own to solve your own problem.

Steve

_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list

bind-users mailing list
bind-...@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

[Kevin Oberman]

On Wed, Oct 2, 2013 at 9:56 PM, Balanagaraju Munukutla <9ba...@sg.ibm.com> wrote:

Hi All

To explain more on the below. We are trying to do a query on MX record for abcd.com.sg. domain to the Authoritative nameserver xxxx.com from my pc. You can see the reply as below. Done this mean that the  Authoritative nameserver xxxx.com failure or this PC where I am doing the query is blocking to communicate that local DNS server configured on it.

Please help.

Thanks & Regards
Nagaraj

Again, all that can be determined is that your PC is not getting a response to it query. There is no information to provide any clue as to whether the PC or the server is at fault.

I would suggest packet capture. On a Windows system, I suggest wireshark. The same for the server, if it is yours. If the server is Unix and you have access to do so, just simple tcpdump will work well. 

[Warren Kumari]

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

> On Wed, Oct 2, 2013 at 9:18 PM, Balanagaraju Munukutla <9ba...@sg.ibm.com> wrote:
>
> Hi
>

> Any one could help on the error below.
>
>
> [andrew@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@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: rkob...@gmail.com

> _______________________________________________
> Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list
>
> bind-users mailing list
> bind-...@lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users

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