Operation timed out when digging mx

Tom bartling at io.com
Fri Aug 15 17:10:19 UTC 2003


Hi,

I'm having a problem with the mx records. If I "dig @ns.realtime.com.
caroldochenrealtors.com.", I get this:

; <<>> DiG 9.2.1 <<>> @ns.realtime.com. caroldochenrealtors.com.
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51346
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0

;; QUESTION SECTION:
;caroldochenrealtors.com.       IN      A

;; ANSWER SECTION:
caroldochenrealtors.com. 2625   IN      A       64.105.113.114

;; AUTHORITY SECTION:
caroldochenrealtors.com. 2625   IN      NS
64.105.113.114.caroldochenrealtors.com.
caroldochenrealtors.com. 2625   IN      NS
64.105.113.115.caroldochenrealtors.com.

;; Query time: 101 msec
;; SERVER: 205.238.128.39#53(ns.realtime.com.)
;; WHEN: Fri Aug 15 12:16:33 2003
;; MSG SIZE  rcvd: 115


However, when I do the same thing, but request the mx records ("dig
@ns.realtime.com. caroldochenrealtors.com. mx"), I get this:

; <<>> DiG 9.2.1 <<>> @ns.realtime.com. caroldochenrealtors.com. mx
;; global options:  printcmd
;; connection timed out; no servers could be reached


Why would it time out for just the mx record on this server? Here's what I
get when I log on to another server (io.com) and "dig
caroldochenrealtors.com. mx":

;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25553
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 0

;; QUESTION SECTION:
;caroldochenrealtors.com.       IN      MX

;; ANSWER SECTION:
caroldochenrealtors.com. 3564   IN      MX      10
mail.caroldochenrealtors.com.
caroldochenrealtors.com. 3564   IN      MX      20 mail.mintecommerce.com.

;; AUTHORITY SECTION:
caroldochenrealtors.com. 3564   IN      NS
64.105.113.114.caroldochenrealtors.com.
caroldochenrealtors.com. 3564   IN      NS
64.105.113.115.caroldochenrealtors.com.

;; Query time: 3 msec
;; SERVER: 199.170.88.10#53(199.170.88.10)
;; WHEN: Fri Aug 15 12:10:35 2003
;; MSG SIZE  rcvd: 155


The lack of consistency is what's making this difficult for me to
troubleshoot. Well... and my lack of experience. Any help would be
appreciated.

TIA,
Tom




More information about the bind-users mailing list