BIND 9.3.2-P1 failing completely on some domains

[Paul A. Hoadley]

On Fri, 15 Sep 2006 18:53:45 -0400, Kevin Darcy
<kcd at daimlerchrysler.com> wrote:

> All of your @a.podbase.com queries are still going to that
> 192.168.0.1 address, so the results you get are rather
> meaningless. What happens if you 1) bounce those same queries
> explicitly off of 85.228.72.199 instead, or

> dig +norec www.eve-files.com @85.228.72.199

; <<>> DiG 9.3.2-P1 <<>> +norec www.eve-files.com @85.228.72.199
; (1 server found)
;; global options:  printcmd
;; connection timed out; no servers could be reached


> dig www.eve-files.com @85.228.72.199

; <<>> DiG 9.3.2-P1 <<>> www.eve-files.com @85.228.72.199
; (1 server found)
;; global options:  printcmd
;; connection timed out; no servers could be reached


> dig +norec www.eve-files.com @85.228.72.199

; <<>> DiG 9.3.2-P1 <<>> +norec www.eve-files.com @85.228.72.199
; (1 server found)
;; global options:  printcmd
;; connection timed out; no servers could be reached


> 2) look up a.podbase.com itself

> dig a.podbase.com

; <<>> DiG 9.3.2-P1 <<>> a.podbase.com
;; global options:  printcmd
;; connection timed out; no servers could be reached

[Interestingly, to me at least, running dig with +trace gives this:

> dig +trace a.podbase.com

; <<>> DiG 9.3.2-P1 <<>> +trace a.podbase.com
;; global options:  printcmd
.                       417180  IN      NS      I.ROOT-SERVERS.NET.
.                       417180  IN      NS      J.ROOT-SERVERS.NET.
.                       417180  IN      NS      K.ROOT-SERVERS.NET.
.                       417180  IN      NS      L.ROOT-SERVERS.NET.
.                       417180  IN      NS      M.ROOT-SERVERS.NET.
.                       417180  IN      NS      A.ROOT-SERVERS.NET.
.                       417180  IN      NS      B.ROOT-SERVERS.NET.
.                       417180  IN      NS      C.ROOT-SERVERS.NET.
.                       417180  IN      NS      D.ROOT-SERVERS.NET.
.                       417180  IN      NS      E.ROOT-SERVERS.NET.
.                       417180  IN      NS      F.ROOT-SERVERS.NET.
.                       417180  IN      NS      G.ROOT-SERVERS.NET.
.                       417180  IN      NS      H.ROOT-SERVERS.NET.
;; Received 388 bytes from 192.168.0.1#53(192.168.0.1) in 2 ms

com.                    172800  IN      NS      D.GTLD-SERVERS.NET.
com.                    172800  IN      NS      E.GTLD-SERVERS.NET.
com.                    172800  IN      NS      F.GTLD-SERVERS.NET.
com.                    172800  IN      NS      G.GTLD-SERVERS.NET.
com.                    172800  IN      NS      H.GTLD-SERVERS.NET.
com.                    172800  IN      NS      I.GTLD-SERVERS.NET.
com.                    172800  IN      NS      J.GTLD-SERVERS.NET.
com.                    172800  IN      NS      K.GTLD-SERVERS.NET.
com.                    172800  IN      NS      L.GTLD-SERVERS.NET.
com.                    172800  IN      NS      M.GTLD-SERVERS.NET.
com.                    172800  IN      NS      A.GTLD-SERVERS.NET.
com.                    172800  IN      NS      B.GTLD-SERVERS.NET.
com.                    172800  IN      NS      C.GTLD-SERVERS.NET.
;; Received 503 bytes from 192.36.148.17#53(I.ROOT-SERVERS.NET) in 49 ms

a.podbase.com.          172800  IN      A       85.228.72.199
podbase.com.            172800  IN      NS      a.podbase.com.
podbase.com.            172800  IN      NS      b.podbase.com.
podbase.com.            172800  IN      NS      c.podbase.com.
podbase.com.            172800  IN      NS      d.podbase.com.
;; Received 173 bytes from 192.31.80.30#53(D.GTLD-SERVERS.NET) in 277 ms

Why can I get an A record for a.podbase.com when tracing is on, and
not without?]

Thanks for your reply Kevin.  I continue to be stumped.


-- 
Paul.

Logic Squad -- Technical Publishing with XML -- http://logicsquad.net/