local_unbound, resolvconf, vpn

[Dag-Erling Smørgrav]

Andriy Gapon <avg at FreeBSD.org> writes:
> First, there is now an automatically generated /etc/resolvconf.conf.
> It has the following comment:
> # This file was generated by local-unbound-setup.
> # Modifications will be overwritten.
> Is that comment really true?
> What and when is going to overwrite my modifications?

service local_unbound setup

> Next. The auto-generated resolvconf.conf has this trick to prevent modifications
> of resolv.conf: resolv_conf="/dev/null"
> The trick works but it causes some small noise when resolvconf is run, like
> cannot copy /dev/null to /dev/null.bak.
> I think that a nicer solution is to just set name_servers=127.0.0.1:

No, if we let resolvconf overwrite resolv.conf then we lose "options
edns0".

What it boils down to is that resolvconf is a piece of shit and the only
way to get it to do what we want would be to write a special backend for
the local_unbound case (see /libexec/resolvconf).

> unbound: [7457:0] error: cannot chdir to directory:  (No such file or directory)

This error is emitted by the configuration parser when it encounters the
"directory" directive in the "server" section and fails to chdir to the
specified directory, but there should be a name there.  Can you do:

# service local_unbound stop
# mv /var/unbound /var/unbound.orig
# mtree -deU -f /etc/mtree/BSD.var.dist
# service local_unbound setup
# diff -ru /var/unbound.orig /var/unbound

and tell me if there are any differences?

DES
-- 
Dag-Erling Smørgrav - des at des.no