Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#42306 - [powerdns] 3.4.0-1 all records appear disabled
Attached to Project:
Community Packages
Opened by Frank Marien (dworkin) - Wednesday, 08 October 2014, 20:38 GMT
Last edited by Alexander F. Rødseth (xyproto) - Friday, 17 October 2014, 09:54 GMT
Opened by Frank Marien (dworkin) - Wednesday, 08 October 2014, 20:38 GMT
Last edited by Alexander F. Rødseth (xyproto) - Friday, 17 October 2014, 09:54 GMT
|
DetailsDescription:
PowerDNS now considers record where disabled IS NULL to be disabled. This disables all records. Additional info: * package v 3.4.0-1 (pdns_control version reports as 3.4.0) * using libgmyqlbackend (fix that first: see * Steps to reproduce: update powerdns to 3.4.0-1. All your records now appear disabled. Powerdns will return the root servers for all queries and commands like pdnssec will tell you the SOA is missing for all domains you attempt to check. Workaround: mysql> use powerdns; mysql> update records set disabled=0 where disabled is null; |
This task depends upon
Closed by Alexander F. Rødseth (xyproto)
Friday, 17 October 2014, 09:54 GMT
Reason for closing: Upstream
Friday, 17 October 2014, 09:54 GMT
Reason for closing: Upstream
Comment by Alexander F. Rødseth (xyproto) -
Thursday, 16 October 2014, 12:54 GMT
Please test with the new 3.4.0-2 package. If that does not change anything, please report upstream to the powerdns developers. https://www.powerdns.com/bugs.html