More on the MX strangeness with 8.2.2

Jim Jagielski jim at devsys.jaguNET.com
Sat Nov 6 01:52:12 UTC 1999


Well, it's not just under A/UX that I'm seeing this problem, I'm
also seeing this under FreeBSD as well. My testcase domain is
'jerkandtheoffs.com' and it's possible that the DNS for that
domain is screwed up and that 8.2.2 is working fine, but the
thing is that 4.9.7 seems to work better.

Under 4.9.7, 'host -d jerkandtheoffs.com' returns:

  ;; res_nmkquery(QUERY, jerkandtheoffs.com, IN, A)
  ;; res_send()
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 31116
  ;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
  ;;      jerkandtheoffs.com, type = A, class = IN
  ;; Querying server (# 1) address = 127.0.0.1
  ;; timeout
  ;; Querying server (# 1) address = 127.0.0.1
  ;; got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 31116
  ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
  ;;      jerkandtheoffs.com, type = A, class = IN
  jerkandtheoffs.com.     1D IN A         206.220.140.93
  jerkandtheoffs.com.     1D IN NS        ns.nyc.datacom.net.
  jerkandtheoffs.com.     1D IN NS        ns.dc.datacom.net.
  ns.nyc.datacom.net.     1D IN A         206.98.165.103
  ns.dc.datacom.net.      1D IN A         205.166.92.2
  rcode = 0 (Success), ancount=1
  jerkandtheoffs.com has address 206.220.140.93
  ;; res_nmkquery(QUERY, jerkandtheoffs.com, IN, MX)
  ;; res_send()
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 31117
  ;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
  ;;      jerkandtheoffs.com, type = MX, class = IN
  ;; Querying server (# 1) address = 127.0.0.1
  ;; got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 31117
  ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 4
  ;;      jerkandtheoffs.com, type = MX, class = IN
  jerkandtheoffs.com.     1D IN MX        20 mail.datacom.net.
  jerkandtheoffs.com.     1D IN MX        10 mail.jerkandtheoffs.com.
  jerkandtheoffs.com.     1D IN NS        ns.nyc.datacom.net.
  jerkandtheoffs.com.     1D IN NS        ns.dc.datacom.net.
  mail.datacom.net.       1D IN A         206.220.140.7
  mail.jerkandtheoffs.com.  1D IN A  206.220.140.93
  ns.nyc.datacom.net.     1D IN A         206.98.165.103
  ns.dc.datacom.net.      1D IN A         205.166.92.2
  rcode = 0 (Success), ancount=2
  jerkandtheoffs.com mail is handled (pri=20) by mail.datacom.net
  jerkandtheoffs.com mail is handled (pri=10) by mail.jerkandtheoffs.com

Now under 8.2.2, getting the MX records gets nasty:

  ;; res_nmkquery(QUERY, jerkandtheoffs.com, IN, A)
  ;; res_send()
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59928
  ;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
  ;;      jerkandtheoffs.com, type = A, class = IN
  ;; Querying server (# 1) address = 127.0.0.1
  ;; got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59928
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0
  ;;      jerkandtheoffs.com, type = A, class = IN
  jerkandtheoffs.com.     23h54m37s IN A  206.220.140.93
  jerkandtheoffs.com.     23h54m37s IN NS  ns.nyc.datacom.net.
  jerkandtheoffs.com.     23h54m37s IN NS  ns.dc.datacom.net.
  rcode = 0 (Success), ancount=1
  jerkandtheoffs.com has address 206.220.140.93
  ;; res_nmkquery(QUERY, jerkandtheoffs.com, IN, MX)
  ;; res_send()
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59929
  ;; flags: rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
  ;;      jerkandtheoffs.com, type = MX, class = IN
  ;; Querying server (# 1) address = 127.0.0.1
  ;; timeout
  ;; Querying server (# 1) address = 127.0.0.1
  ;; timeout
  res_nsend failed

Now one thing to note is that the NSs for the domains do not,
themselves, resolve to any valid IP address. If I try a simple
'dig jerkandtheoffs.com mx -debug -d2' the 4.9.7 server will
correctly respond but the 8.2.2 one will:

    ; <<>> DiG 8.2 <<>> jerkandtheoffs.com mx -debug -d2 
    ;; res options: init recurs defnam dnsrch
    ;; res_nsend[signed] to server default -- 127.0.0.1: Operation timed out

Again, the DNS setup for this domain might be screwy, but 4.9.7
seems to handle it :/
-- 
===========================================================================
   Jim Jagielski   [|]   jim at jaguNET.com   [|]   http://www.jaguNET.com/
                "Are you suggesting coconuts migrate??"


More information about the bind-workers mailing list