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.
DescriptionChristophe Besson
2019-10-02 09:43:21 UTC
Description of problem:
After an upgrade to RHEL 7.7, lookup tools behavior has changed, the search domain from resolv.conf isn't appended when resolving a wildcard entry (whereas ping does). It seems to be a regression since that works with the previous tools coming with RHEL 7.6 (bind-utils-9.9.4-74.el7_6.2.x86_64). Please note that building and using the previous version on RHEL 7.7 works as expected (downgrade won't work due to deps).
Version-Release number of selected component (if applicable):
bind-utils-9.11.4-9.P2.el7.x86_64
How reproducible:
* Setup a named server with a "bar" domain:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
# dig bar axfr
; <<>> DiG 9.11.4-P2-RedHat-9.11.4-9.P2.el7 <<>> bar axfr
;; global options: +cmd
bar. 3600 IN SOA master.bar. root.master.bar. 2019100201 28800 1200 604800 3600
bar. 3600 IN NS master.bar.
foo.bar. 3600 IN A 10.0.0.2
master.bar. 3600 IN A 10.0.0.1
wildcard.bar. 3600 IN A 10.10.10.10
*.wildcard.bar. 3600 IN A 10.10.10.10
bar. 3600 IN SOA master.bar. root.master.bar. 2019100201 28800 1200 604800 3600
;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Oct 02 05:36:03 EDT 2019
;; XFR size: 7 records (messages 1, bytes 236)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
* Configure your local resolver with:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
search bar
nameserver 127.0.0.1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Actual results:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
# host foo
foo.bar has address 10.0.0.2
# host wildcard
wildcard.bar has address 10.10.10.10
# host foo.wildcard
Host foo.wildcard not found: 3(NXDOMAIN)
# host foo.wildcard.bar
foo.wildcard.bar has address 10.10.10.10
# ping foo.wildcard
PING foo.wildcard.bar (10.10.10.10) 56(84) bytes of data.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Expected results:
Like it was on RHEL 7.6 with the previous version of bind-utils.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
# host foo.wildcard
foo.wildcard.bar has address 10.10.10.10
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Additional info:
Comment 3Christophe Besson
2019-10-02 10:00:33 UTC
Same as #1743572
I didn't see it before filing this bug.