Re: local_unbound, resolvconf, vpn

2017-11-21 Thread Dag-Erling Smørgrav
Alexander Zagrebin writes: > Also I have to notice that there is another issue with the default > local_unbound setup: > by default unbound uses syslog for logging, but usually the > local_unbound service starts before syslogd and so logging doesn't work > until local_unbound will be reloaded. Th

Re: local_unbound, resolvconf, vpn

2017-11-20 Thread Alexander Zagrebin
Hi! Also I have to notice that there is another issue with the default local_unbound setup: by default unbound uses syslog for logging, but usually the local_unbound service starts before syslogd and so logging doesn't work until local_unbound will be reloaded. So it's looks reasonable to use log

Re: local_unbound, resolvconf, vpn

2017-11-20 Thread Dag-Erling Smørgrav
Andriy Gapon writes: > Did you do the import of unbound 1.5.10 before or after 11.1? FreeBSD 10 has 1.5.7. FreeBSD 11 and 12 both have 1.5.10. > It seems that the chdir code was not present in the earlier version that we > had. It was added in 1.5.10, only a few hours after 1.5.9 was released

Re: local_unbound, resolvconf, vpn

2017-11-20 Thread Andriy Gapon
On 20/11/2017 16:43, Dag-Erling Smørgrav wrote: > Andriy Gapon writes: >> Dag-Erling Smørgrav writes: >>> Andriy Gapon writes: What and when is going to overwrite my modifications? >>> service local_unbound setup >> So, this is not going to happen automatically (after the initial setup) ? >

Re: local_unbound, resolvconf, vpn

2017-11-20 Thread Dag-Erling Smørgrav
Andriy Gapon writes: > Dag-Erling Smørgrav writes: > > Andriy Gapon writes: > > > What and when is going to overwrite my modifications? > > service local_unbound setup > So, this is not going to happen automatically (after the initial setup) ? > I have to manually run that command? Currently, y

Re: local_unbound, resolvconf, vpn

2017-11-20 Thread Andriy Gapon
On 08/11/2017 14:17, Alexander Zagrebin wrote: > This message appears because you are using chroot. > You have to edit /var/unbound/unbound.conf and add a trailing slash to > value of the 'directory' parameter: That did it! > server: > ... > chroot: /var/unbound > directory: /var/unbo

Re: local_unbound, resolvconf, vpn

2017-11-20 Thread Andriy Gapon
On 13/11/2017 15:55, Dag-Erling Smørgrav wrote: > Andriy Gapon 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 tru

Re: local_unbound, resolvconf, vpn

2017-11-13 Thread Dag-Erling Smørgrav
Andriy Gapon 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 modificatio

Re: local_unbound, resolvconf, vpn

2017-11-08 Thread Alexander Zagrebin
В Wed, 8 Nov 2017 13:38:28 +0200 Andriy Gapon пишет: > I've just enabled local_unbound on a machine and everything seems to > work fine. But there are a few minor quirks that I would like to > report. > Last. Every time I connect to a VPN (via vpnc or openvpn, for > exmaple) the unbound daemon

local_unbound, resolvconf, vpn

2017-11-08 Thread Andriy Gapon
I've just enabled local_unbound on a machine and everything seems to work fine. But there are a few minor quirks that I would like to report. First, there is now an automatically generated /etc/resolvconf.conf. It has the following comment: # This file was generated by local-unbound-setup. # Modi