Your message dated Sun, 28 Oct 2012 22:09:41 +0100
with message-id <[email protected]>
and subject line Closing very old bind9 bugs
has caused the Debian Bug report #129873,
regarding bind9 refuses to send NOTIFY to slaves
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
129873: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=129873
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bind9
Version: 9.2.0
Severity: serious

It seems bind9 refuses to send NOTIFY to slaves. Asking for help
on comp.protocols.dns.bind did not lead to any fixes either and
a few comments from others who have the same problem so this does
indeed seem to be a real bug. This is the post I made there
describing the problem:

I have a problem with bind 9.2.0 and slave servers: I have a few
zones setup on ns1.ams.attingo.nl, with ns.hoho.nl and ns2.hoho.nl
as slave servers. Both slaves are allowed to transfer the zones
properly (we tested that).

The problem is that the master (ns1.ams.attingo.nl) refuses to
send NOTIFYs to the slaves. I do get this in my logs:

Jan 17 13:38:29 zaphod named[23848]: no IPv6 interfaces found
Jan 17 13:38:29 zaphod named[23848]: zone freenet.ams.attingo.nl/IN: loaded 
serial 11
Jan 17 13:38:29 zaphod named[23848]: zone freenet.ams.attingo.nl/IN: sending 
notifies (serial 11)

But note that it does not list the servers it should send the NOTIFY to.

The zone is setup like this:

------------------------------------------------------------------------
@               IN      SOA     ns1.ams.attingo.nl. hostmaster.attingo.nl. (
                                10      ; Serial
                                8H      ; Refresh
                                1H      ; Retry
                                1W      ; Expire
                                1D )    ; Default TTL
                IN      NS      ns1.ams.attingo.nl.
                IN      NS      ns.hoho.nl.
                IN      NS      ns2.hoho.nl.

------------------------------------------------------------------------

If anyone can give me some hints as to what the problem might
be I'ld be grateful, I've been staring at this for a while now
and I can't figure out what the problem is.

Wichert.

-- 
  _________________________________________________________________
 /       Nothing is fool-proof to a sufficiently talented fool     \
| [email protected]                   http://www.liacs.nl/~wichert/ |
| 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0  2805 3CB8 9250 2FA3 BC2D |


--- End Message ---
--- Begin Message ---
Since this bug references a BIND 9 version that is even older than
oldstable (lenny) I'm closing it. 

Please reopen if reproducible in newer versions.

--- End Message ---

Reply via email to