[Pdns-users] recursor: no reverse lookups

Mon Nov 19 10:49:52 UTC 2018

Frank,

thank you for your input. I thought it could go in this direction (recursor is by definition non-auth), and – well, I think I don’t have to care about that. But I’ll read more of the theory of auth/non-auth and it’s impact.

   Sig

Von: Pdns-users <pdns-users-bounces at mailman.powerdns.com> Im Auftrag von Frank Louwers via Pdns-users
Gesendet: Montag, 19. November 2018 09:16
An: pdns-users at mailman.powerdns.com
Betreff: Re: [Pdns-users] recursor: no reverse lookups

Sig,

First of all it’s best not to use nslookup. It can produce unpredictable and sometimes false results. Please use a tool like “dig” or “drill”.

Is 192.168.94.66#53 the authoritative server for that 94.168.192.in-addr.arp domain? If so, then yes, the result is an authoritative answer, as the auth-server provided that answer.

Your pdns-recursor in front of it, is a recursor,  so the result is non-auth.

Hope this helps…

Frank Louwers

On 19 Nov 2018, at 09:03, Sig Pam <spam at itserv.de> wrote:

One more thing. Maybe you have a quick idea, I did not run through the docs for that.

Asking my DNS for a reverse address gives an authoritative answer:

[root at hallo ~]# nslookup

> server sixtysix 

Default server: sixtysix

Address: 192.168.94.66#53

> 192.168.94.123

Server:         sixtysix

Address:   192.168.94.66#53

123.94.168.192.in-addr.arpa     name = fileserver.corp.domain.de.

Asking pdns-recursor is a non-authoritative answer

> set port=5300

> 192.168.94.123

Server:         sixtysix

Address:   192.168.94.66#5300

Non-authoritative answer:

123.94.168.192.in-addr.arpa     name = fileserver.corp.domain.de.

Authoritative answers can be found from:

Any quick idea? 

   Sig

-----Ursprüngliche Nachricht-----
Von: Sig Pam 
Gesendet: Montag, 19. November 2018 08:53
An: bert hubert <bert.hubert at powerdns.com>; Sig Pam <spam at itserv.de>
Cc: pdns-users at mailman.powerdns.com
Betreff: AW: [Pdns-users] recursor: no reverse lookups

Bert,

thank you very much. That seems to be the solution for my issue. I was aware of this switch and played with it sooner, without success. But this was in another test environment, potentially with more hidden problem.

Great! Again, thank you!

  Sig

-----Ursprüngliche Nachricht-----

Von: bert hubert <bert.hubert at powerdns.com> 

Gesendet: Sonntag, 18. November 2018 19:57

An: Sig Pam <spam at itserv.de>

Cc: pdns-users at mailman.powerdns.com

Betreff: Re: [Pdns-users] recursor: no reverse lookups

On Sun, Nov 18, 2018 at 04:10:52PM +0100, bert hubert wrote:

> On Sun, Nov 18, 2018 at 03:00:53PM +0000, Sig Pam wrote:

> > [root at hallo ~]# nslookup - 192.168.94.66

> > 

> > > set port=53

> > 

> > > 192.168.94.66

Ok, I see it now, try adding: serve-rfc1918=off

What you are seeing is that the powerdns recursor is answering your

192.168.in-addr.arpa queries itself.

        Bert

_______________________________________________
Pdns-users mailing list
Pdns-users at mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users

_______________________________________________

Pdns-users mailing list

Pdns-users at mailman.powerdns.com

https://mailman.powerdns.com/mailman/listinfo/pdns-users