named.service - BIND Domain Name Server
Loaded: loaded (/lib/systemd/system/named.service; disabled; vendor preset: disabled)
Active: failed (Result: signal) since Wed 2022-11-30 05:41:15 EST; 2s ago
Duration: 31ms
Docs: man:named(8)
Process: 19521 ExecStart=/usr/sbin/named -f $OPTIONS (code=killed, signal=ABRT)
Main PID: 19521 (code=killed, signal=ABRT)
CPU: 33ms

Nov 30 05:41:15 kali systemd[1]: named.service: Scheduled restart job, restart counter is at 5.
Nov 30 05:41:15 kali systemd[1]: Stopped BIND Domain Name Server.
Nov 30 05:41:15 kali systemd[1]: named.service: Start request repeated too quickly.
Nov 30 05:41:15 kali systemd[1]: named.service: Failed with result 'signal'.
Nov 30 05:41:15 kali systemd[1]: Failed to start BIND Domain Name Server.

Hi, and welcome here, at LQ
I would like to ask you why did you show us it? Do you have a question or request?
For troubleshooting I would suggest you to follow this: http://www.catb.org/~esr/faqs/smart-...html#beprecise
Regarding kali I would recommend this:https://www.linuxquestions.org/quest...ad-4175614092/
Additionally you may try: https://duckduckgo.com/?q=Failed+to+...&kae=-1&ia=web

idk systemd, there are many "nested wrapped" things so that what config file was loaded isn't seen in your logfile

bind will quit if the configuration files are not right. that will depend on your bind version, "what configs are ok", obviously.

"Start request repeated too quickly" looks like systemd tried to restart the failed process without waiting, thus the "too quickly". usually that means a script error on the part of systemd / those who provided startup boot rc scripts. One way to get that is (on older systems) to have /etc/inittab say to start something if it's not running, that fails to load, then you get such a message.

In other words: good luck. You'll need to see systemd manuals, run through allot of config, and or if lucky google if someone else had the same problem.