Re: Bind 8.3.4 logging

Elijah Savage wrote:

> All I have setup a primary nameserver ok no big deal. But before when I
> was doing this on older versions I sware it use to log message in
> /var/log/messages about a notify when you change the serial and reload
> but this version is not giving me that. I looked through the archives
> and could not find anything in reference to this so I also broke open
> DNS&Bind 4th Edition and it says on page 262 it should do this without
> any special configs in named.conf
>
> So I changed the serial again and reloaded but this time I was snooping
> on the interface for port 53 traffic and I see the notify go out. But
> then right after I get this message back, and it is not one I have seen
> before from my slave name server=20
> 12273 NotImp*- 0/0/0 (33)
>
> Does anyone have a clue what this is?

Well, "NotImp" is probably your sniffer's interpretation of the "NOTIMP"
RCODE (4), "0/0/0" is probably its interpretation of the record counts in
the Answer, Authority and Additional sections. I'm not sure what the rest
means, including the asterisk.

If you really are getting a NOTIMP response from your slave, then this
implies it's running a very ancient version of BIND or some
non-BIND software that doesn't implement the NOTIFY extension.

> Also can someone send me a copy of what a successful xfer looks like
> because my isp is my secondary and I am not sure if he is actually
> pulling my zone files.

What, you want the entire contents of a zone transfer posted to the
list?!?!?! Why not just do a zone transfer from your master (using the
"axfr" query type in "dig" or an "ls" command in "nslookup") and sniff the
packets? This will show you what the contents of an AXFR transaction looks
like. The only other things which might distinguish this from what's
actually happening between your master and its slaves, other than NOTIFY,
are a) there will be an SOA query and response preceding the actual zone
transfer, b) if the slave understands IXFR (Incremental Zone Transfer),
then you may get that instead of the more traditional AXFR, c) if the
slave understands the "many-answers" transfer format and you have
configured that particular slave in named.conf to use "many-answers", then
the zone transfer format will differ from the traditional
"one-answer" format.


- Kevin