Add gpgkey_dns_verification=true to /etc/dnf/dnf.conf Expected: ➜ ~ sudo dnf update --refresh DNSSEC extension: Testing already imported keys for their validity. Fedora - Rawhide - Developmental packages for the next Fedora release 47 kB/s | 12 kB 00:00 Dependencies Resolved ... See behavior: DNSSEC extension: Testing already imported keys for their validity. DNSSEC extension: GPG Key fedora-27 could not be verified, because DNSSEC signatures are bogus. Possible causes: wrong configuration of the DNS server, MITM attack DNSSEC extension: GPG Key fedora-28 could not be verified, because DNSSEC signatures are bogus. Possible causes: wrong configuration of the DNS server, MITM attack DNSSEC extension: GPG Key linux-packages-keymaster could not be verified, because DNSSEC signatures are bogus. Possible causes: wrong configuration of the DNS server, MITM attack DNSSEC extension: GPG Key fedora-29 could not be verified, because DNSSEC signatures are bogus. Possible causes: wrong configuration of the DNS server, MITM attack DNSSEC extension: GPG Key fedora-30-primary could not be verified, because DNSSEC signatures are bogus. Possi ble causes: wrong configuration of the DNS server, MITM attack DNSSEC extension: GPG Key fedora-31-primary could not be verified, because DNSSEC signatures are bogus. Possi ble causes: wrong configuration of the DNS server, MITM attack DNSSEC extension: GPG Key fedora-32-primary could not be verified, because DNSSEC signatures are bogus. Possible causes: wrong configuration of the DNS server, MITM attack DNSSEC extension: GPG Key linux-packages-keymaster could not be verified, because DNSSEC signatures are bogus. Possible causes: wrong configuration of the DNS server, MITM attack DNSSEC extension: GPG Key fedora-33-primary could not be verified, because DNSSEC signatures are bogus. Possible causes: wrong configuration of the DNS server, MITM attack ... Nothing seems to be wrong with fedoraproject.org dnssec: https://dnssec-debugger.verisignlabs.com/fedoraproject.org
I guess it's the same underlying issue as discussed with Florian Weimer on the mailing list, i.e. dnssec caching by the stub resolver for local unicast dns clients.
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle. Changing version to 33.
This happens with both default DNSSEC=no and DNSSEC=yes in resolved.conf.
It would be partially fixed in F34, when DNSSEC=yes. It would be still broken with default settings. It seems no plan to fix this in Fedora 33 exists, it should work with other local caches, ie. with dnsmasq and unbound.
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Still unfixed in f34 without DNSSEC validation enabled in systemd. Which is not required, since unbound library is doing its own validation.
in f35, first there is https://bugzilla.redhat.com/show_bug.cgi?id=2018913 concretely systemd-resolved stub is not used for gpgkey_dns_verification (so if above bug is fixed, I guess you should see reoccurrence of this bug) After doing rm /etc/resolv.conf ln -s /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf resolvectl dns eth0 8.8.8.8 and activating the dns verification, I get the "bogus" thing. I make it more verbose with: https://github.com/rpm-software-management/dnf/pull/1796 which can actually display where the bogus is coming from: DNSSEC signatures are wrong (validation failure <e27f1efe21ae589b7796e61af3ac4a4c1c2428615daca70d8f1c9e96._openpgpkey.fedoraproject.org. OPENPGPKEY IN>: SERVFAIL no DS for DS org. while building chain of trust) I guess this is what above comment refers to > dnssec caching by the stub resolver for local unicast dns clients. this can be worked around by deactivating LLMNR: $ dig org SOA +short $ sudo resolvectl llmnr eth0 false $ dig org SOA +short a0.org.afilias-nst.info. noc.afilias-nst.info. 2014593646 1800 900 604800 86400 $ dnf -d 10 update DNSSEC extension: Testing already imported keys for their validity. Running verification for key with id: fedora-35-primary DNSSEC extension: GPG Key fedora-35-primary is valid
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Still present on rawhide, when default DNSSEC=no is used. Even if forwarders are capable just fine.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 37 development cycle. Changing version to 37.
This message is a reminder that Fedora Linux 37 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '37'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 37 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 37 entered end-of-life (EOL) status on None. Fedora Linux 37 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.
DNSSEC extension: Testing already imported keys for their validity. DNSSEC extension: GPG Key fedora-40-primary could not be verified, because DNSSEC signatures are bogus. Possible causes: wrong configuration of the DNS server, MITM attack Sadly this is still present issue.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 40 development cycle. Changing version to 40.
This message is a reminder that Fedora Linux 40 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 40 on 2025-05-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '40'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 40 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 40 entered end-of-life (EOL) status on 2025-05-13. Fedora Linux 40 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.