On 4/2/20 12:49 PM, Alan Batie via Pdns-users wrote:
I'm in the process of migrating to powerdns to take advantage of the
supermaster/superslave feature in particular (as well as better dnssec
management), with a hidden master architecture to provide additional
security for administration and d
Hello,
we are using a PowerDNS Authoritative master together with two superslaves.
Clients only query the slaves through a PowerDNS Recursor so they are not aware
of the master. The master is not part of the autoritative nameserver set in any
of the zones.
I just found this issue that the supe
I'm in the process of migrating to powerdns to take advantage of the
supermaster/superslave feature in particular (as well as better dnssec
management), with a hidden master architecture to provide additional
security for administration and dnssec private keys. It seems, however,
that for the
Hi,
thanks Chris for your advice.
We are planning to migrate to PowerDNS (from bind) primarily because of
APIs: my opinion is that using subdomain/zone pairs is a cleaner approach,
isn't it?
Thanks a lot!
On Mon, 30 Mar 2020 at 11:02, Chris via Pdns-users <
pdns-users@mailman.powerdns.com> wro
Hi Kevin,
On 4/2/20 1:54 PM, Kevin P. Fleming via Pdns-users wrote:
> I just realized that by accident I've been adding a port number in
> local-ipv6, and it's been working as I intended, even though the
> documentation does not say that port numbers can be included in
> local-address or local-ipv
I just realized that by accident I've been adding a port number in
local-ipv6, and it's been working as I intended, even though the
documentation does not say that port numbers can be included in
local-address or local-ipv6.
I currently have a server listening on 127.0.0.1:53 and [ipv6
GUA]:5353 a
