Description of problem: Periodic timer of unbound-anchor is running to maintain root trust anchor daily. However it requires direct connection to root servers, it would never try local forwarders. If that machine is running in environment with restricted direct connection to both DNS servers and HTTPS at data.iana.org, RFC 5011 would not work. Version-Release number of selected component (if applicable): unbound-0:1.6.0-6.fc25.x86_64 How reproducible: Always Steps to Reproduce: 1. Block access to all DNS servers but your forwarders. 2. Block HTTPS connection to data.iana.org. 3. systemctl start unbound-anchor Actual results: /var/lib/unbound/root.key is not modified systemctl status unbound-anchor shows failed local DNS server is never tried Expected results: /var/lib/unbound/root.key is modified with update timestamp local DNS server is checked for DNSSEC support first Additional info: I think it should prefer local DNS server and only try direct root query if it fails. It can delay new key fetch by local DNS server cache. It will reduce load of root servers. It will work on intranets without direct access to the Internet if local forwarders support DNSSEC.
Yes, this is important to get fixed before the KSK roll and the end of the year.
Created attachment 1285746 [details] Simple unbound-anchor fix Simple workaround to using local DNS configuration first and direct root access only if that fails. It would make working RFC7958 if direct root queries are not available.
Note: It is not required to block HTTPS. Without direct DNS access, it cannot resolve and validate data.iana.org. It fails also RFC 7958 fallback according to my testing. I think that was not intended. I reset owner as I lack commit rights for unbound now.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.