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.

Bind fails to validate a configuration file when host bits in CIDRs are set (e.g. 172.17.1.1/24). This is a regression after updating from bind-9.11.4-26.P2.el8 (RHEL 8.1) to bind-9.11.13-3.el8 (RHEL 8.2).

This upstream cherry-pick appears to have introduced the regression:
https://github.com/isc-projects/bind9/commit/42f998ee14bab9fb8db32f17e59409d4a9593e74

Version-Release number of selected component (if applicable):
bind-9.11.13-3.el8

How reproducible: 100%

Steps to Reproduce:
1. Install bind-9.11.13-3.el8
2. Use sample configuration file in "Additional info" below
3. Validate configuration file with "named-checkconf"

Actual results:

named-checkconf exits with status error code.

# named-checkconf bad.conf; echo $?
bad.conf:6: '172.17.1.1/24': address/prefix length mismatch '24'
1


Expected results:

This is the result when downgraded to bind-9.11.4-26.P2.el8:

# named-checkconf bad.conf; echo $?
bad.conf:6: '172.17.1.1/24': address/prefix length mismatch
0

Additional info:

# cat bad.conf 
controls  {
        inet 172.17.1.98 port 953 allow { 172.17.1.1/24; };
};

FYI, there is an upstream fix for this already merged on the v9_11 branch that I have confirmed resolves the issue:

https://gitlab.isc.org/isc-projects/bind9/-/commit/7e2d9531a79d289ee99dd436da14efb6d9a505fc

$ ./named-checkconf bad-named.conf 
bad-named.conf:4: '192.168.24.1/24': address/prefix length mismatch
[johnsom@workstation check]$ echo $?
0

Checking out the SHA before 7e2d9531a79d289ee99dd436da14efb6d9a505fc shows the regression:

$ ./named-checkconf /tmp/bad-named.conf 
/tmp/bad-named.conf:4: '192.168.24.1/24': address/prefix length mismatch '24'
[johnsom@workstation check]$ echo $?
1

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 (Moderate: bind security, bug fix, and enhancement update), 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://access.redhat.com/errata/RHSA-2020:4500