named.conf Default Location?
Tony Finch
dot at dotat.at
Wed Jan 13 11:09:19 UTC 2016
Tim Daneliuk <tundra at tundraware.com> wrote:
>
> The manpage for named on machine 1 says that it looks for the named.conf
> by default in /usr/local/etc/namedb. Machine 2's manpage says it looks
> in /etc/namedb.
>
> Which is correct? Is the /etc/namedb symlink even needed anymore?
The man pages should be correct, but if you don't trust them you can
verify what really happens in two ways:
(1) Run named -V and it should tell you the arguments to the configure
script. Look for --sysconfdir or --prefix. These determine where named
looks for named.conf, as described in the README:
You may specify the option "--sysconfdir" to set the directory
where configuration files like "named.conf" go by default,
and "--localstatedir" to set the default parent directory
of "run/named.pid". For backwards compatibility with BIND 8,
--sysconfdir defaults to "/etc" and --localstatedir defaults to
"/var" if no --prefix option is given. If there is a --prefix
option, sysconfdir defaults to "$prefix/etc" and localstatedir
defaults to "$prefix/var".
(2) Run:
strings `which named` | grep named.conf
Tony.
--
f.anthony.n.finch <dot at dotat.at> http://dotat.at/
South Fitzroy: Cyclonic becoming northerly later, 5 to 7, occasionally gale 8.
Rough or very rough. Rain. Moderate or poor.
More information about the bind-users
mailing list