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.
Description of problem:
"hostname --fqdn" fails if there are no IPv4 address on the host. (it works well on RHEL7).
Version-Release number of selected component (if applicable):
net-tools-1.60-110.el6_2.x86_64
(hostname-3.13-3.el7.x86_64 is not affected)
How reproducible: Always
Steps to Reproduce:
1. Make sure there are no IPv4-addresses set up on the host in /etc/hosts, DNS or rDNS.
2. run "tcpdump port 53 &"
3. run "hostname --fqdn"
Actual results:
There is an ?A-request to the nameserver, but no ?AAAA-request
Hostname fails to provide the FQDN
Expected results:
"hostname --fqdn" should provide the FQDN if it's set up with IPv6 in /etc/hosts
"hostname --fqdn" should provide the FQDN if it's set up with IPv6 in DNS and rDNS.
Additional info:
Workaround: set up the FQDN on 127.0.0.1 in /etc/hosts
Created attachment 1213378[details]
Patch
I crafted a patch which resolves this problem. It uses the getaddrinfo function instead of deprecated gethostbyname. gethostbyname is used only for getting aliases for debug output. The debug output which is changed in the latest hostname stays as it is and is not affected by this change.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2017-0600.html