Hi, I'm not sure if this is the same or a different error as the original, but this is the 2nd hit on google when looking for my problem.
I was using a hidden master and the SOA had the name of the slave in it. (There was only 1 NS in the zone.) bind didn't send out any notification, but it did when I added an also-notify entry in the config file. Once I change the SOA not to have the name of the slave in it things worked as expected. Kurt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
