error in named.service failed

[theseagull]

i was following this guide to bind dns server
https://www.unixmen.com/dns-server-setu ... s-7-linux/
but i got this error
https://envs.sh/QZ5.jpeg

[scottro]

I don't have the answer to your question, but firstly, it helps if you mention that you're using WSL on Windows, at least I assume so from the screen shot.
Secondly, since you are doing it in Winows, you're much better off copying and pasting the error. Many people on this list are quite busy and won't bother going to a screenshot, whereas, if you had text in the post, they would be more likely to look.

That will probably get you more (and helpful) answers, than the screenshot does.

[jlehtone]

BIND 9 has probably very fine features but I have found dnsmasq to be much simpler to set up, yet sufficient for humble needs.
So, do you need a DNS server, or do you need the BIND?

[Whoever]

i was following this guide to bind dns server
https://www.unixmen.com/dns-server-setu ... s-7-linux/
but i got this error
https://envs.sh/QZ5.jpeg

I have rarely found the information from the journalctl and systemctl commands useful when dealing with this type of issue. I suspect that if you run:

Code: Select all

grep named /var/log/messages

you may find the information there more informative.

[jlehtone]

I have rarely found the information from the journalctl and systemctl commands useful when dealing with this type of issue.

That ought to be about formatting and filtering. Those commands get data from systemd-journal.service. The rsyslog.service, which writes files like the /var/log/messages, seems to get data from systemd-journal.service too.

Some services do not use these facilities (for everything), but write logs to their own log files directly. For example, httpd and samba. For those cases one really has to "go to files".

[TrevorH]

This appears to be running on Windows so I am not sure that /var/log/messages will exist. I'm also not sure we support this as there is no official CentOS support in WSL.

[Whoever]

I have rarely found the information from the journalctl and systemctl commands useful when dealing with this type of issue.

That ought to be about formatting and filtering. Those commands get data from systemd-journal.service. The rsyslog.service, which writes files like the /var/log/messages, seems to get data from systemd-journal.service too.

Maybe there is some way to get the data in a well formatted fashion, with all the lines I need from the systemd commands, but why? grep on the files in /var/log works well and gives me everything I need. Perhaps the developers of systemd chose some poor defaults for the commands; I don't see why I should work around their bad choices when I have an alternative.