192.168.68.63/64 are authoritative-only servers (pdns auth) for internal domains. You are right that currently the resolver does not make sense But the idea is to have in the future a file forward-zones-file of the type test1.com=192.168.1.1 test2.com=192.168.1.2 .=192.168.68.63, 192.168.68.64
El jue, 17 mar 2022 a las 16:38, Brian Candler (<b.cand...@pobox.com>) escribió: > On 17/03/2022 15:26, Pepe Charli wrote: > > In the traces only the domain has been changed to test.com > 192.168.68.63 and 192.168.68.64 are autoritatives for this domain. > Both resolver and authoritative are only used internally with private > IPs > > Are 192.168.68.63/64 authoritative-only servers (like pdns auth), or > mixed recursor+authoritative (like bind)? > > If they are authoritative-only, this implies the recursor can never > resolve a public DNS name. In that case, the recursor seems to serve little > purpose: you could point the clients directly at the authoritatives, or use > dnsdist to forward the queries. > > If they are mixed, and you want to be able to resolve names in the public > DNS, then you will need "+." in your forward-zones-file in the pdns > recursor. > >
_______________________________________________ Pdns-users mailing list Pdns-users@mailman.powerdns.com https://mailman.powerdns.com/mailman/listinfo/pdns-users
