-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
rhel-7.9.z, rhel-7-els
-
None
-
Yes
-
Critical
-
rhel-sst-cs-net-perf-services
-
ssg_core_services
-
None
-
False
-
-
None
-
None
-
None
-
None
-
None
What were you trying to do that didn't work?
Unable to start bind after updating it.
What is the impact of this issue to you?
bind daemon down, DNS down
Please provide the package NVR for which the bug is seen:
bind-9.11.4-26.P2.el7_9.17.x86_64
older versions does not present this problem.
How reproducible is this bug?:
Always
Steps to reproduce
- Have a zone with more than 100 items in a single resource record or more than 100 resources record of the same type.
- # systemctl start named
Expected results
named service starting correctly.
[root@r79 ~]# systemctl start named [root@r79 ~]#
Actual results
named service does not start and shows error in a zone "too many records"
[root@r79 ~]# systemctl start named Job for named.service failed because the control process exited with error code. See "systemctl status named.service" and "journalctl -xe" for details.
More details:
● named.service - Berkeley Internet Name Domain (DNS) Loaded: loaded (/usr/lib/systemd/system/named.service; disabled; vendor preset: disabled) Active: failed (Result: exit-code) since Mon 2024-10-28 14:56:51 -03; 8s ago Process: 1660 ExecStartPre=/bin/bash -c if [ ! "$DISABLE_ZONE_CHECKING" == "yes" ]; then /usr/sbin/named-checkconf -z "$NAMEDCONF"; else echo "Checking of zone files is disabled"; fi (code=exited, status=1/FAILURE)Oct 28 14:56:51 r79 bash[1660]: dns_master_load: db.x.x:1167: IN.x.x.in-addr.arpa: too many records Oct 28 14:56:51 r79 bash[1660]: dns_master_load: db.x.x:1167: IN.x.x.in-addr.arpa: too many records Oct 28 14:56:51 r79 bash[1660]: dns_master_load: db.x.x:1167: IN.x.x.in-addr.arpa: too many records Oct 28 14:56:51 r79 bash[1660]: zone x.x.in-addr.arpa/IN: loading from master file db.x.x failed: too many records Oct 28 14:56:51 r79 bash[1660]: zone x.X.in-addr.arpa/IN: not loaded due to errors. Oct 28 14:56:51 r79 bash[1660]: _default/x.x.in-addr.arpa/IN: too many records Oct 28 14:56:51 r79 systemd[1]: named.service: control process exited, code=exited status=1 Oct 28 14:56:51 r79 systemd[1]: Failed to start Berkeley Internet Name Domain (DNS). Oct 28 14:56:51 r79 systemd[1]: Unit named.service entered failed state. Oct 28 14:56:51 r79 systemd[1]: named.service failed.
Additional information:
We should have options (max-records-per-type, max-types-per-name) at the configuration level to manage those imposed limits as bind will not load with proper customer settings.
Solution is to downgrade bind* or migrate into RHEL 9.