Skip to main content ↑ ↓
Topic: bind and runit: small error in default configuration (Read 402 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

bind and runit: small error in default configuration

hi,
i installed bind and bind-runit to play with and have a local cache/resolver
when running
Code: [Select]
sv start named
It failed. named wasn't started.
I looked in daemon.log and saw that named complained about named.conf not existing in /etc/named/named.conf
In fact, when installing the package "bind", the default named.conf is written in /etc/named.conf, while the run script from bind-runit launches  "named -c /etc/named/named.conf" .
So, it 's easy to fix once installed, but it might confuse some user  :D

Re: bind and runit: small error in default configuration

Reply #1 –
For local resolving+caching may I suggest dnsmasq or even tinydns, which in my box consumes only 4MB - in comparison, supervise-daemon which controls tinydns occupies 15MB.
 

Re: bind and runit: small error in default configuration

Reply #2 –
Hi nous,
It was not for a long term, just testing how it performs under artix, and managing it with runit.
And indeed, if i needed a local resolver/cache, dnsmasq is a good one. thanks for pointing tinydns, i didn't know about it :)
Finally, in my humble opinion, the default configuration file in the bind package should be /etc/named/named.conf. it's usually this on all the other distros i have used