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.
Bug 1297562 - WKS records cannot be parsed with bind-chroot installed
Summary: WKS records cannot be parsed with bind-chroot installed
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: bind
Version: 6.7
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: rc
: ---
Assignee: Petr Menšík
QA Contact: Petr Sklenar
URL:
Whiteboard:
Depends On:
Blocks: 1392362
TreeView+ depends on / blocked
 
Reported: 2016-01-11 21:30 UTC by Dan Astoorian
Modified: 2017-03-21 10:06 UTC (History)
3 users (show)

Fixed In Version: bind-9.8.2-0.59.rc1.el6
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1392362 (view as bug list)
Environment:
Last Closed: 2017-03-21 10:06:23 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
named.wks (230 bytes, text/plain)
2016-10-26 15:25 UTC, Petr Menšík 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0651 0 normal SHIPPED_LIVE bind bug fix update 2017-03-21 12:32:44 UTC

Description Dan Astoorian 2016-01-11 21:30:04 UTC 
Description of problem:
With bind-chroot installed, zone files containing WKS records are rejected with "unknown protocol" errors.

Version-Release number of selected component (if applicable):
bind-chroot-9.8.2-0.37.rc1.el6_7.5.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Add a WKS record to an existing zone file; /var/named/named.localhost will do.  E.g., 
    echo -e '\tWKS 127.0.0.1 TCP (smtp)' >> /var/named/named.localhost
2. yum install bind-chroot
3. service named start

Actual results:
Starting named: 
Error in named configuration:
dns_rdata_fromtext: named.localhost:11: near 'TCP': unknown protocol
zone localhost.localdomain/IN: loading from master file named.localhost failed: unknown protocol
zone localhost.localdomain/IN: not loaded due to errors.
_default/localhost.localdomain/IN: unknown protocol
dns_rdata_fromtext: named.localhost:11: near 'TCP': unknown protocol
zone localhost/IN: loading from master file named.localhost failed: unknown protocol
zone localhost/IN: not loaded due to errors.
_default/localhost/IN: unknown protocol
zone 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN: loaded serial 0
zone 1.0.0.127.in-addr.arpa/IN: loaded serial 0
zone 0.in-addr.arpa/IN: loaded serial 0
                                                           [FAILED]


Expected results:
Starting named:                                            [  OK  ]


Additional info:
Note that if the bind-chroot package is removed, named will start up successfully.

The problem is caused by the inability of the chroot'd environment to look up protocols and services (in /etc/protocols and /etc/services, respectively).

It appears that for 64-bit systems, creating the directory /var/named/chroot/lib64/ and changing:

ROOTDIR_MOUNT='/etc/named /etc/pki/dnssec-keys /var/named /etc/named.conf /etc/named.dnssec.keys /etc/named.rfc1912.zones /etc/rndc.conf /etc/rndc.key /usr/lib64/bind /usr/lib/bind /etc/named.iscdlv.key /etc/named.root.key'

to:

ROOTDIR_MOUNT='/etc/named /etc/pki/dnssec-keys /var/named /etc/named.conf /etc/named.dnssec.keys /etc/named.rfc1912.zones /etc/rndc.conf /etc/rndc.key /usr/lib64/bind /usr/lib/bind /etc/named.iscdlv.key /etc/named.root.key /etc/services /etc/protocols /lib64/libnss_files.so.2'

in /etc/rc.d/init.d/named may be sufficient to allow named to launch.  (This probably presumes the user is using the default NSS backend for protocols and services; if /etc/nsswitch.conf has been customized, the adjustments may not be as straightforward.)

A similar issue may exist in Red Hat Enterprise Linux 7 (I first encountered it in CentOS 7; I do not have an installed RHEL7 system to test against).
Comment 5 Petr Menšík 2016-10-26 15:25:09 UTC 
Created attachment 1214323 [details]
named.wks

Minimal zone to reproduce failure. With bind-chroot installed, it will prevent bind from starting.
Save it to /var/named
Just yum install -y bind-chroot

and add to named.conf

zone "wks.localdomain" IN {
        type master;
        file "named.wks";
        allow-update { none; };
};
Comment 14 errata-xmlrpc 2017-03-21 10:06:23 UTC 
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-0651.html
Note You need to log in before you can comment on or make changes to this bug.