Red Hat Bugzilla – Bug 507469
host command does not report errors with a specified server
Last modified: 2013-04-30 19:43:43 EDT
Although a specific server was given on the command line, the host command fell back on the backup servers in /etc/resolv.conf instead of reporting the error from the server. For example:
amcnabb@maggie:~% host mcnabbs.org 10.0.0.10
Using domain server:
mcnabbs.org has address 18.104.22.168
mcnabbs.org mail is handled by 5 mail.mcnabbs.org.
According to the man page for host, "server is an optional argument which is either the name or IP address of the name server that host should query instead of the server or servers listed in /etc/resolv.conf."
bind-dyndb-ldap-0.1.0-0.2.a1.fc11, dnsperf-22.214.171.124-10.fc11, bind-9.6.1-2.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update bind-dyndb-ldap dnsperf bind'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-6766
I did "yum --enablerepo=updates-testing update bind-dyndb-ldap dnsperf" and ran "host" and got:
host: error while loading shared libraries: liblwres.so.50: cannot open shared object file: No such file or directory
It looks like bind-libs-9.6.1-2.fc11.x86_64 has a broken symlink:
amcnabb@prodigy:~% ls -l /usr/lib64/liblwres*
lrwxrwxrwx 1 root root 18 2009-07-02 15:06 /usr/lib64/liblwres.so.50 -> liblwres.so.50.2.0
-rwxr-xr-x 1 root root 73336 2009-06-24 08:58 /usr/lib64/liblwres.so.50.0.2
It looks like the symlink should point at liblwres.so.50.0.2 instead of liblwres.so.50.2.0.
I fixed this symlink by hand and noticed another broken symlink:
root@prodigy:/usr/lib64# ls -l libbind9*
lrwxrwxrwx 1 root root 18 2009-07-02 15:06 libbind9.so.50 -> libbind9.so.50.2.0
-rwxr-xr-x 1 root root 41808 2009-06-24 08:58 libbind9.so.50.0.3
After fixing this one by hand, too, host seems to run again.
Other than the broken library symlinks, the update seems to fix the original bug.
Interesting, bind-libs in repositories is correct. Would it be possible to try `rpm -e --nodeps bind-libs`, `yum install bind-libs` and check if symlinks are correct, please?
After uninstalling and reinstalling bind-libs, the symlinks are correct. That's very strange (I never touched the symlinks by hand).
bind-dyndb-ldap-0.1.0-0.2.a1.fc11, dnsperf-126.96.36.199-10.fc11, bind-9.6.1-2.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.