Re: wildcard dnssec test fails

Hi Viktor, On 20/12/17 09:15, Viktor Dukhovni via Unbound-users wrote: > On Tue, Dec 19, 2017 at 06:08:50AM +, Viktor Dukhovni wrote: > >> The original coded uses non-portable undefined overflow behaviour >> for signed integer arithmetic. The compiler is free to replace >> "incep - expi >

Re: wildcard dnssec test fails

On Tue, Dec 19, 2017 at 06:08:50AM +, Viktor Dukhovni wrote: > The original coded uses non-portable undefined overflow behaviour > for signed integer arithmetic. The compiler is free to replace > "incep - expi > 0" with "incep > expi". The intermediate "var" > may in some cases avoid the

Re: wildcard dnssec test fails

On Fri, Dec 15, 2017 at 11:40:38AM +0100, W.C.A. Wijngaards wrote: > Yes it is the compiler. Clang fails, gcc succeeds. I can make clang > succeed with a small code change together with the removal of -O2 > (disabling clang's optimizer). > > The code change is instead of if(incep - expi > 0)

Re: wildcard dnssec test fails

Hi, Thanks so much for finding the problem. I've recompiled unbound with GNU gcc for now. It seamed like the simplest solution.  I never would have thought that the access to a internet service (to the end user) could be broken because of a compiler optimisation. Still so many things have to

Re: wildcard dnssec test fails

Hi, Wait, no, just CFLAGS=-g ./configure disables -O2, but you also need the code change. So that won't work as a workaround. Best regards, Wouter On 15/12/17 11:40, W.C.A. Wijngaards via Unbound-users wrote: > Hi Sebastian > > On 15/12/17 10:19, Sebastian Schmidt via Unbound-users wrote: >>

Re: wildcard dnssec test fails

Hi Sebastian On 15/12/17 10:19, Sebastian Schmidt via Unbound-users wrote: > On 15 December 2017 at 6:09:19 pm, W.C.A. Wijngaards via Unbound-users > (unbound-users@unbound.net ) wrote: >> When I run unbound-host, I get no errors,  >> ./unbound-host  

Re: wildcard dnssec test fails

On 15 December 2017 at 6:09:19 pm, W.C.A. Wijngaards via Unbound-users (unbound-users@unbound.net) wrote: When I run unbound-host, I get no errors,  ./unbound-host  www.wilda.nsec.0skar.czwww.wilda.nsec.0skar.cz -f  root.key -v -t A  www.wilda.nsec.0skar.czwww.wilda.nsec.0skar.cz has address 

Re: wildcard dnssec test fails

Hi Sebastian, Viktor, On 15/12/17 01:26, Viktor Dukhovni via Unbound-users wrote: > On Thu, Dec 14, 2017 at 02:21:15PM +1000, Sebastian Schmidt wrote: > >> I�ve unbound setup on FreeBSD 11.1 and I can�t figure out why "drill >> www.wilda.nsec.0skar.cz" gives SERVFAIL. The domain is from this >>

Re: wildcard dnssec test fails

On Thu, Dec 14, 2017 at 02:21:15PM +1000, Sebastian Schmidt wrote: > I�ve unbound setup on FreeBSD 11.1 and I can�t figure out why "drill > www.wilda.nsec.0skar.cz" gives SERVFAIL. The domain is from this > (http://0skar.cz/dns/en) test site where it reports three failures (2a, > 2b and 4). Any

Re: wildcard dnssec test fails

Hi Paul, > Is your unbound configured to use another DNS as forwarder? Yes, to nsd for opennic TLDs which to my understanding should not impact this query. Here is the config file: # This file is managed by Ansible. # # template:

Re: wildcard dnssec test fails

On Thu, 14 Dec 2017, Sebastian Schmidt via Unbound-users wrote: I’ve unbound setup on FreeBSD 11.1 and I can’t figure out why "drill www.wilda.nsec.0skar.cz" gives SERVFAIL. The domain is from this (http://0skar.cz/dns/en) test site where it reports three failures (2a, 2b and 4). Any help

wildcard dnssec test fails

Hello, I’ve unbound setup on FreeBSD 11.1 and I can’t figure out why "drill www.wilda.nsec.0skar.cz" gives SERVFAIL. The domain is from this (http://0skar.cz/dns/en) test site where it reports three failures (2a, 2b and 4). Any help would be appreciated. Thanks Sebastian $ unbound -h