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#41149 - [bind] DNSSEC broken
Attached to Project:
Arch Linux
Opened by Daniel Petre (dape) - Wednesday, 09 July 2014, 21:36 GMT
Last edited by Sébastien Luttringer (seblu) - Tuesday, 23 September 2014, 20:52 GMT
Opened by Daniel Petre (dape) - Wednesday, 09 July 2014, 21:36 GMT
Last edited by Sébastien Luttringer (seblu) - Tuesday, 23 September 2014, 20:52 GMT
|
DetailsDescription:
with bind-9.10.0.P2-1 DNSSEC is okay, with bind-9.10.0.P2-1 it is broken. |
This task depends upon
Closed by Sébastien Luttringer (seblu)
Tuesday, 23 September 2014, 20:52 GMT
Reason for closing: Not a bug
Additional comments about closing: No able to reproduce. Nobody complains about that.
Tuesday, 23 September 2014, 20:52 GMT
Reason for closing: Not a bug
Additional comments about closing: No able to reproduce. Nobody complains about that.
If this is an upstream bug, I suggest you to report them directly and to fallback to the previous version waiting they provide a fix.
My setup is simple, a local bind cache on a dual core 64bit up-to-date Arch Linux with 2 Gb of ram and 512 Mb reserved for bind. Nothing in logs..
dnssec-enable yes;
dnssec-validation yes;
dnssec-lookaside auto;
Other than that nothing special..
If last bind release break DNSSEC, I imagine we receive more complain.