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

[Pieter Lexis]

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 an error in powerdns recursor is
> that the checker on dnsflagday.net tells me "This domain is going to
> work after February 1st 2019" when I check p4.no.
> 
> 
> Recursor 4.1.12 accepts the zone:
> 
> $ host p4.no dnscache1
> Using domain server:
> Name: dnscache1
> Address: 2001:700:300::200#53
> Aliases:
> 
> p4.no has address 213.179.55.103
> p4.no has address 213.179.55.102
> p4.no has IPv6 address 2001:820:2::a:102
> p4.no has IPv6 address 2001:820:2::a:103
> p4.no mail is handled by 20 p4-no.mx2.comendosystems.net.
> p4.no mail is handled by 10 p4-no.mx1.comendosystems.com.
> 
> 
> Recursor 4.2.0-beta1 doesnt:
> 
> $ host p4.no dnscachetest01
> Using domain server:
> Name: dnscachetest01
> Address: 129.241.190.20#53
> Aliases:
> 
> Host p4.no not found: 2(SERVFAIL)
> 
> 
> Is powerdns recursor 4.2 or dnsflagday.net correct here?

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?

Best regards,

Pieter