Re: [Pdns-users] recursor 4.2.0-beta1 fails to resolve p4.no

Pieter Lexis writes: > I tested the wrong domain. p4.no indeed breaks because the auths respond > with a FORMERR plus an OPT record when EDNS is sent in the query. The > flagday site indeed does not seem to check this, but it is wrong > behaviour. Thank you! I'll contact the admin with a link t

Re: [Pdns-users] pdnsutil and MySQL connection aborted

On Wed, May 08, 2019 at 05:27:34PM +0200, Thomas Plant via Pdns-users wrote: > Hello, > > I installed PDNS 4.1.8 fresh from the powerdns repos. Configured MySQL > and for testing I imported our ~3000 domains into pdns using pdnsutil > load-zone. > All was imported happily, data is just fine. But e

[Pdns-users] pdnsutil and MySQL connection aborted

Hello, I installed PDNS 4.1.8 fresh from the powerdns repos. Configured MySQL and for testing I imported our ~3000 domains into pdns using pdnsutil load-zone. All was imported happily, data is just fine. But every time I use the pdnsutil I see the following error from MySQL: May  8 17:15:14 pdns1

Re: [Pdns-users] recursor 4.2.0-beta1 fails to resolve p4.no

Hi Øystein, On 5/8/19 9:50 AM, Pieter Lexis wrote: > I can resolve p4.no without issue on 4.2.0. Can you start the recursor > with the `trace` option set and provide the logs if it still fails? I tested the wrong domain. p4.no indeed breaks because the auths respond with a FORMERR plus an OPT rec

Re: [Pdns-users] recursor 4.2.0-beta1 fails to resolve p4.no

Pieter Lexis writes: > I can resolve p4.no without issue on 4.2.0. Can you start the recursor > with the `trace` option set and provide the logs if it still fails? Still fails for me. Logs here: http://folk.ntnu.no/ov/p4.no.txt Thanks, Øystein __

Re: [Pdns-users] recursor 4.2.0-beta1 fails to resolve p4.no

Hi Brian, They do work if you specify +noedns Frank > On 8 May 2019, at 10:46, Brian Candler wrote: > > On 08/05/2019 09:07, Brian Candler wrote: >> From here (UK), that domain looks a bit broken - see the FORMERR response >> from the authoritative servers. I have tried from two different ne

Re: [Pdns-users] recursor 4.2.0-beta1 fails to resolve p4.no

On 08/05/2019 09:07, Brian Candler wrote: From here (UK), that domain looks a bit broken - see the FORMERR response from the authoritative servers.  I have tried from two different networks and get the same response. The nameserver A records for this domain are also toast.  The glue records

Re: [Pdns-users] recursor 4.2.0-beta1 fails to resolve p4.no

Hi Pieter, I can confirm it does NOT work on my 4.2.0-beta1 (Debian version from the PDNS repo). Trace logs can be found here: https://gist.github.com/franklouwers/cd310d80fef603394cc2fb77d3098fb5 Kind Regards, Frank > On 8 May 2019, at 09:50, Pieter Lexis wrote: > > Hi Øystein, > > > I

Re: [Pdns-users] recursor 4.2.0-beta1 fails to resolve p4.no

On 08/05/2019 08:50, Pieter Lexis wrote: I can resolve p4.no without issue on 4.2.0. From here (UK), that domain looks a bit broken - see the FORMERR response from the authoritative servers.  I have tried from two different networks and get the same response. brian@ns1:~$ dig @x.nic.no. p4

Re: [Pdns-users] recursor 4.2.0-beta1 fails to resolve p4.no

Hi Øystein, On 5/8/19 9:42 AM, Øystein Viggen wrote: > I initially discovered this when running the 4.1.x recursor release that > had the dns flag day changes. P4 is a popular Norwegian radio station, > so with some 50k users there were some complaints.. > > The thing that makes me think this is

[Pdns-users] recursor 4.2.0-beta1 fails to resolve p4.no

Hi! I initially discovered this when running the 4.1.x recursor release that had the dns flag day changes. P4 is a popular Norwegian radio station, so with some 50k users there were some complaints.. The thing that makes me think this is an error in powerdns recursor is that the checker on dnsfl