Re: Getting error messages, DNSSEC appears to be working nevertheless

2017-07-24 Thread Beeblebrox via Unbound-users
Hi Wouter & thanks for the insight. I apparently overlooked some items when going through the /var/unbound/unbound.conf settings. I had (root-hints: "/var/unbound/root.hints") commented out, so I no longer need this flag in /etc/rc.conf: "-r '/var/unbound/root.hints'" I took out the "-a"

Re: error: outgoing tcp: bind: Address already in use

2017-07-24 Thread W.C.A. Wijngaards via Unbound-users
Hi Nick, On 21/07/17 05:29, Nick Urbanik via Unbound-users wrote: > Dear Folks, > > On 06/07/17 18:13 +1000, Nick Urbanik via Unbound-users wrote: >> A DNS server running unbound 1.6.3 has these messages; any suggestions >> on what is happening? >> >> error: serviced_tcp_initiate: failed to send

Re: Getting error messages, DNSSEC appears to be working nevertheless

2017-07-24 Thread W.C.A. Wijngaards via Unbound-users
Hi Beeblebrox, I think the issue is that -a adds the root.key file, but you also have the root.key file in your unbound.conf, hence it is added twice. You'd need another unbound.conf file without the root.key statement for unbound-anchor. (unbound.conf supports include: "file" to make that easy

Getting error messages, DNSSEC appears to be working nevertheless

2017-07-24 Thread Beeblebrox via Unbound-users
Hello. I have Unbound running in a FreeBSD Jail, with all required files placed in /var/unbound. /etc/rc.conf starts unbound with: unbound_enable="YES" unbound_flags="-c /var/unbound/unbound.conf" unbound_anchorflags="-a '/var/unbound/root.key' -C /var/unbound/unbound.conf -r