dns query fails if there are more than 100 records of the same type or named/named-chroot fails to start with error "too many records"
Issue
- dns query to a named server fails, if there are more than 100 records of the same RR type.
- named/named-chroot fails to start with error "too many records".
- named service is in failed state due to high number of entries in a zone. This was working fine on before updating named package. Below errors are observed in journal logs.
Sep 25 11:23:40 node-0.rhel810.lab bash[25560]: dns_master_load: db.10.reverse:4920: 246.164.10.10.in-addr.arpa: too many records
Sep 25 11:23:40 node-0.rhel810.lab bash[25560]: dns_master_load: db.10.reverse:5020: 247.164.10.10.in-addr.arpa: too many records
Sep 25 11:23:40 node-0.rhel810.lab bash[25560]: zone 10.in-addr.arpa/IN: loading from master file db.10.reverse failed: too many records
Sep 25 11:23:40 node-0.rhel810.lab bash[25560]: zone 10.in-addr.arpa/IN: not loaded due to errors.
Sep 25 11:23:40 node-0.rhel810.lab bash[25560]: _default/10.in-addr.arpa./IN: too many records
Sep 25 11:23:40 node-0.rhel810.lab systemd[1]: named.service: Control process exited, code=exited status=1
Sep 25 11:23:40 node-0.rhel810.lab systemd[1]: named.service: Failed with result 'exit-code'
Environment
- Red Hat Enterprise Linux 7 (RHEL 7)
- bind-9.11.4-26.P2.el7_9.17
- Red Hat Enterprise Linux 8 (RHEL 8)
- bind-9.11.36-16.el8_10.2
- bind-9.11.36-8.el8_8.6
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.