Hi,
mufurcz wrote:
Greetings,
A disk in one of the old firewalls (not exactly critical) failed
(running OpenBSD 2.9!), and I urgently
need a DNS server to work. Replaced the disk and installed 4.2.
Starting `named -g` (listing below),
produces a few surprising messages, like:
a) line 3: BIND trying to load the configuration from /etc an not from
/var/named/etc (my understanding
was that the default -c option looks for the named.config in
/var/named/etc an not in /etc);
This is because named is chrooted by default.
b) lines 34 and 35: `could not open entropy source /dev/arandom: file
not found` and `using pre-chroot
entropy source /dev/arandom` complaining about a missing
/var/named/dev/arandom device.
I think this has to do with the chroot as well. I get this too, and no
harm seems to be done.
/Alexander