I well know the scenario 3, but it means to either reconfigure the clients to point to the new DNS recursor, or reconfigure the domains and masters/slave servers in order to point to the new DNS auth.
My point here is not technical, I well know theses possibilities. The problem is that on 90% of installations (generally bind installations), the sites are using the same addresses for auth and recursor function. So for me the problem is do I still can use powerdns as replacement for bind without reconfiguring the whole DNS setup on curstomer’s sites. Regards, Alain RICHARD > Le 19 janv. 2018 à 18:53, Brian Candler <b.cand...@pobox.com> a écrit : > > On 19/01/2018 17:36, Alain RICHARD wrote: >> Scenario 1 : the recursor is on port 53 and forward queries from known >> zones to the authoritative pdns on port 5300 >> >> Scenario 2 : the dnsdist is on port 53, forward queries from known zones to >> the authoritative pdns on port 5300, and forward recursive queries to the >> recursor on port 5301 > > Scenario 3: put an alias IP address on the server, and bind the recursor and > auth servers to different addresses. > _______________________________________________ Pdns-users mailing list Pdns-users@mailman.powerdns.com https://mailman.powerdns.com/mailman/listinfo/pdns-users
