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.
(In reply to rhayden from comment #1)
> Potentially related bug at
> https://bugzilla.redhat.com/show_bug.cgi?id=1743572
>
> Discussion on using the "options ndots:3" in /etc/resolv.conf to relax the
> security stance.
That works here too.
I assumed the issue was exclusive to TXT records due to how the issue was observed on the customer's environment, sorry about that. I just tested for an A record and I see the same behavior (the ndots workaround is also good then).
It seems this bug may be actually a duplicate then.
Would close it as a duplicate. However, this issue would be fixed in RHEL 7, since it originally worked there. But such thing never worked in RHEL 8.
We currently do not have plan to fix it in RHEL8, since upstream considers it a bad habbit to include dots in search directive queries. Search was supposed to search bare name without a dot in current set of domains. It would work well with www or ftp, but not www.subdomain or ldap.division.
General recommendation is to use full absolute anywhere and not to rely on search or domain directives in /etc/resolv.conf. They might be reconfigured by DHCP, which is not secured in any way. Full domains are safer in this mode, because it either resolves or fails. It is not passed to every search domain first or as a final try. We would like to keep it so.
It it is important feature you cannot overcome, feel free to reopen the bug. But please explain how you use it and why full name is not possible to use.
Until that, closing as not a bug.