Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
+++ This bug was initially created as a clone of Bug #2226054 +++
dnssec-trigger checks whether servers provided by the network allow DNSSEC validation enabled on them. If the tests results in a server not supporting DNSSEC (it is not security-aware), it tries to configure alternative servers used for resolution. Those alternative servers were provided by unbound running on 3 fedora servers, but they were not maintained enough.
Because it turned out some features were not provided functional for some time, it were decided to shutdown them. Most networks today should be already prepared for validating end clients.
In case they are not, there are quite many open public resolvers offering encrypted or unencrypted resolution, which should work better for majority of users.
A good list of resolvers is at:
https://dnsprivacy.org/public_resolvers/
Reproducible: Always
Steps to Reproduce:
1. systemctl restart dnssec-triggerd
2. dnssec-trigger-control test_tcp
3. dnssec-trigger-control test_ssl
Actual Results:
Resolution breaks, it does not work anymore. It can be fixed by systemctl restart dnssec-triggerd.
Expected Results:
Resolution should be redirected to working server, which still provides connectivity to public resolvers.
All needed is update of /etc/dnssec-trigger/dnssec-trigger.conf. There comment out previous uncommented lines starting with tcp80: or ssl443: and instead insert upstream provided server:
# provided by NLnetLabs
# It is provided on a best effort basis, with no service guarantee.
tcp80: 185.49.140.67
tcp80: 2a04:b900::10:0:0:67
ssl443: 185.49.140.67 7E:CF:B4:BE:B9:9A:56:0D:F7:3B:40:51:A4:78:E6:A6:FD:66:0F:10:58:DC:A8:2E:C0:43:D4:77:5A:71:8A:CF
ssl443: 2a04:b900::10:0:0:67 7E:CF:B4:BE:B9:9A:56:0D:F7:3B:40:51:A4:78:E6:A6:FD:66:0F:10:58:DC:A8:2E:C0:43:D4:77:5A:71:8A:CF
I think we want to add simple way to support DNS over TLS servers in a modern way. That is without those weird hashes, but instead validating a name of a server and CA chain of its certificate. Just like for normal TLS services, for example in HTTPS. A separate bug #2223972 is filled for that.
--- Additional comment from Fedora Update System on 2023-07-25 20:57:50 CEST ---
FEDORA-EPEL-2023-10397fd427 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-10397fd427
Comment 1RHEL Program Management
2023-09-21 18:58:44 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 2RHEL Program Management
2023-09-21 19:06:09 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.