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

On Fri, May 10, 2019 at 05:13:32PM +0200, Otto Moerbeek wrote: > > Hello, > > please do not use html mail for mailing lists. Especially if the > plain/text alternatie is empty. Below you can see what the mail looks > like in mutt. Thanks! > > The copying semantics of the RC (and CD) bits are de

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

Hello, please do not use html mail for mailing lists. Especially if the plain/text alternatie is empty. Below you can see what the mail looks like in mutt. Thanks! The copying semantics of the RC (and CD) bits are described in https://tools.ietf.org/html/rfc6895 In general 1034 and 1035 only c

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

Hello Steinar,> if I query without the "Recursion Desired" flag, the flag is still set in the replyThanks for that. Ill remove it.(I don't see in the RFC that it shouldnt be allowed to include it, but it doesnt make any sense)> There are multiple problems ... https://ednscomp.isc.org/ednscompWe do

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

> (I am the author of the mentioned dns software) > > According to RFC1034, including the request in the response seem to be > required. Is there something I am misunderstanding here ? There are multiple problems with p4.no, and you can see it with the ISC EDNS compliance tester: https://edn

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

Hello Pieter,(I am the author of the mentioned dns software)According to RFC1034, including the request in the response seem to be required.Is there something I am misunderstanding here ?4.3.1. Queries and responses The principal activity of name servers is to answer standard queries. Both the que

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] 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