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

[Charles Swiger]

Hi--

On Oct 2, 2013, at 9:18 PM, Balanagaraju Munukutla <9balan at sg.ibm.com> wrote:
> 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 

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