Bug 1848169

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; };
};