Documentation Question for Dig

[Kevin Darcy]

I think you're dealing with 2 different issues here:

1. The "not zone top" error means you tried to do a zone transfer of something
that technically wasn't a zone. For example, if you have a name www.foo.com in
the foo.com zone, which is not a delegated subzone, and then tried to do a
zone transfer, you'd get a refusal with the "not zone top" message, just as
you are experiencing.

2. For some reason, your version of dig is choking on the REFUSED response
from the server. I'm not sure why that is -- I just tested it with the dig
that came with BIND 8.1.2, with BIND 8.2.2-p5 and an ancient old "2.1" version
of dig, and none of them had any problems. Mind you, I only tried this against
BIND 8.2.2-p5 servers; maybe there's some sort of server-side dependency here.
So what *exact* version of dig are you using? My guess is the dig problem will
be moot if you fix the underlying problem (#1, above), so maybe you don't care
to spend time and effort troubleshooting/debugging it...


- Kevin

lee.stone at hqasc.army.mil wrote:

> Is there a source for or information page that contains definitions for DIG
> status messages. For example, while working with a domain administrator and
> trying to DIG an axfr of a specific zone.
> I am receiving the following error status.
>
> dig @100.100.100.101 xxx.yyyyyyy.zzzz.www axfr
>
> ; <<>> DiG 8.1 <<>> @100.100.100.101 xxx.yyyyyyy.zzzz.www axfr
> ; (1 server found)
> ;; ns_initparse: Message too long
> ;; Received 0 answers (0 records).
> ;; FROM: gggggggg-ccc52 to SERVER: 100.100.100.101
> ;; WHEN: Tue Jul 25 07:50:25 2000
>
> The DNS server is logging "not zone top" and dening the axfr request.
>
> Thanks in advance
>
> Lee Stone