Re: libsystemd not found an error

2018-07-31 Thread Wouter Wijngaards via Unbound-users
Hi Yoshihito Horigome, On 07/31/2018 04:43 PM, Yoshihito Horigome via Unbound-users wrote: > Hello, > > Wouter-san, > > I delayed to reply. > > When pkg-config is specified as below, configure now passes. It is nice that configure works. The sd_is_socket_sockaddr function was added in Dec

Re: 1.7.3 - stub-zone public domain

2018-07-31 Thread Wouter Wijngaards via Unbound-users
Hi, On 07/27/2018 06:19 PM, ѽ҉ᶬḳ℠ via Unbound-users wrote: > >> is stub-zone is only serving private domains but not public domains? stub zones and forward zones are selected closest to the name of the query.  That one is used. If you run another (authoritative) server on

Re: libsystemd not found an error

2018-07-31 Thread Yoshihito Horigome via Unbound-users
Hello, Wouter-san, I delayed to reply. When pkg-config is specified as below, configure now passes. $ sudo ./configure --with-libevent --with-ssl --disable-static --sysconfdir=/etc/unbound --with-conf-file=/etc/unbound/unbound.conf --with-pidfile=/var/run/unbound.pid --enable-pie

Re: 1.7.3 - stub-zone public domain

2018-07-31 Thread ѽ҉ᶬḳ℠ via Unbound-users
> You have a name set for the forward zone, and it looks up the name > "dns." that you set. It does not exist, so won't do anything. Just > remove that from the config if you do not want it to look that up. > forward-host is meant to be able to give the name string that unbound > looks up

Re: Unbound and Logitech Media Server: Couldn't resolve IP address

2018-07-31 Thread Wouter Wijngaards via Unbound-users
Hi Bern, If it keeps happening, try setting verbosity 4, then unbound prints more and more debug information what is going on. I guess it is unable to get replies from the network. I don't really know what is going on either. Best regards, Wouter On 07/05/2018 06:57 AM, Bern D via

Re: DNS-over-TLS IPv4 interface ceases to respond

2018-07-31 Thread Guillaume-Jean Herbiet via Unbound-users
Thanks for the quick reply. We build our own kernels for those servers (currently using 4.16.13), so it is rather recent (compared to 3.10 from CentOS). I will disable so-reuseport, maintain extra logging on this server and see if it happens again. On 2018-07-31 09:46, Wouter Wijngaards via

DNS-over-TLS IPv4 interface ceases to respond

2018-07-31 Thread Guillaume-Jean Herbiet via Unbound-users
Hello, We are using Unbound 1.7.3 to test the DNS-over-TLS service and advance options (see specifications and config file below). The server is generally on very low use (avg. 2 queries/s) but configured following the optimization guide[1] in order to test options and perform stress tests.

Re: DNS-over-TLS IPv4 interface ceases to respond

2018-07-31 Thread Wouter Wijngaards via Unbound-users
Hi, On 07/31/2018 09:07 AM, Guillaume-Jean Herbiet via Unbound-users wrote: > Hello, > > We are using Unbound 1.7.3 to test the DNS-over-TLS service and advance > options (see specifications and config file below). > > The server is generally on very low use (avg. 2 queries/s) but > configured

1.7.3: capsforid fallback response confusion

2018-07-31 Thread Alex Zorin via Unbound-users
Hi, Came across the curious case of a domain that appears to cause Unbound to compare responses of different qtypes in process_response during caps-for-id fallback. This can be reproduced with Unbound 1.7.3 with qname-minimization (strict), and use-caps-for-id. $ unbound-host