On Tuesday 27 September 2005 20:48, Marc Sherman wrote:
> My guess is that the 30 second delay is the timeout while your DNS
> server fails to resolve the domain xxxxxx.
Thanks, but not that, I don't think (dns lookup in <1s - see below).
(Sorry for removing domain name, it seemed irrelevant as delays on a number of
domains, but point taken.)
rich
----------8<------------------------------------
$ time dig shinyblue.net MX
; <<>> DiG 9.3.1 <<>> shinyblue.net MX
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 14792
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 3
;; QUESTION SECTION:
;shinyblue.net. IN MX
;; ANSWER SECTION:
shinyblue.net. 86400 IN MX 30 mail.shinyblue.net.
;; AUTHORITY SECTION:
shinyblue.net. 86400 IN NS ns.34sp.com.
shinyblue.net. 86400 IN NS ns2.34sp.com.
;; ADDITIONAL SECTION:
mail.shinyblue.net. 86400 IN A 195.50.105.121
ns.34sp.com. 86400 IN A 212.187.158.3
ns2.34sp.com. 86400 IN A 212.100.224.247
;; Query time: 669 msec
;; SERVER: 168.95.1.1#53(168.95.1.1)
;; WHEN: Tue Sep 27 21:13:07 2005
;; MSG SIZE rcvd: 143
real 0m0.681s
----------8<------------------------------------
rich
