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.

Description of problem:
It was reported on upstream mailing list [1] for name goededoelennederland.nl. This issue is fixed in most recent version since 2.82, commit [2].

Version-Release number of selected component (if applicable):
dnsmasq-2.79-15.el8.x86_64

How reproducible:
Reliable

Steps to Reproduce:
1. Add log-queries, dnssec and conf-file=/usr/share/dnsmasq/trust-anchors.conf to dnsmasq.conf
2. systemctl restart dnsmasq
3. dig @localhost goededoelennederland.nl

Actual results:
dig timeout
log contains repeated key requests

Expected results:
Name resolved with only few queries

Additional info:
Resolving fails, because DNSKEY has TTL 0:
$ dig dnskey goededoelennederland.nl

; <<>> DiG 9.16.11-RedHat-9.16.11-6.fc32 <<>> dnskey goededoelennederland.nl
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11126
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;goededoelennederland.nl.	IN	DNSKEY

;; ANSWER SECTION:
goededoelennederland.nl. 0	IN	DNSKEY	257 3 13 XJK1tle+SOcz93UPMJj4VcbgJkfoMLkrrxfdJ66Us1p3IUtUpkSgK7sM ghbMg/pJJ5TNr3ixfDVRZZlYxy393A==


1. https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2021q1/014858.html
2. http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=7e194a0a7d483932eb3f416b8f26131ade588acc

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.