Package: pdns Version: 2.9.20-8 Severity: normal When a zone gets deleted from a (MySQL backended) supermaster nameserver, the accompanying slave nameservers (also configured with a MySQL backend) get confused when doing a periodic retrieve/refresh of the zone: > May 14 06:37:25 callisto pdns[17268]: Error trying to retrieve/refresh > 'mydomain.nl': Remote nameserver reported error: RCODE=2
The supermaster reports that it's not authoritative, which is correct: > May 14 06:37:25 helios pdns[31590]: Not authoritative for 'mydomain.nl', > sending servfail to 123.123.123.123 This bug causes the slave nameserver to continue serving this zone, which is absolutely not desirable and in fact renders the slave/supermaster infrastructure unusable. The slave nameserver will probably stop serving the domain after the configured expire-period (SOA, usually 2-4 weeks). Note that in in some countries you are obligated to remove a zone from your nameservers within a few days, otherwise the domain won't be released by the domain registration authority (for example, the .nl cctld). This bug forces you to manually update the slave nameserver configuration, which is obviously not the idea behind the slave/supermaster setup! I think the slave nameservers should remove a zone from their databases when a supermaster starts throwing NXDOMAIN-errors on retrieve/refresh. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-xen-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages pdns depends on: ii pdns-recursor 3.1.4-1 PowerDNS recursor ii pdns-server 2.9.20-8 extremely powerful and versatile n pdns recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
