Red Hat Bugzilla – Bug 150765
bind-utils missing resolver.5 manpage
Last modified: 2007-11-30 17:07:06 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Description of problem:
The bind-utils pages traditionally carries a resolver.5 manpage so that
"man resolv.conf" and "man 5 resolver" produce some output. This appears to not be the case in RHEL3
old.box# cat /etc/redhat-release
Red Hat Linux release 7.2 (Enigma)
old.box# rpm -qf /usr/share/man/man5/resolver.5.gz
new.box# cat /etc/redhat-release
Red Hat Enterprise Linux WS release 3 (Taroon Update 4)
new.box# rpm -qf /usr/share/man/man5/resolver.5.gz
error: file /usr/share/man/man5/resolver.5.gz: No such file or directory
new.box# rpm -q bind-utils
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Actual Results: no manpage
Expected Results: resolver.5 manpage is shown
Yes, sorry - there appears to have been some communication failure
with the glibc maintainers . GLIBC should be providing the
documentation of its resolver, and the glibc maintainers had agreed
to do so, but evidently did not apply this to RHEL-3.
The resolver.5 manpage provided by BIND dated from 1993 and was
hopelessly out of date. I'll get an updated resolver man-page
into the RHEL-3 man-pages for the next release .
The resolver(5) man-page is not shipped in ISC BIND .
BIND does not implement the resolver functionality : glibc does.
Previously, we had shipped a very out-of-date resolver man-page (from 1991 !)
copied from the BSD man-pages, which caused much confusion amongst users.
The man-pages package (or glibc) needs to ship the up-to-date resolver man-page
in RHEL-3 .
BIND should not ship an out-of-date resolver man-page. We need to ship
up-to-date documentation for the resolver, as is done for the
resolver(3) man-page, in man-pages.
Created attachment 115041 [details]
Suggested resolver.5 man-page
*** Bug 155695 has been marked as a duplicate of this bug. ***
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.