If someone will have the same issue, the answer is here:
https://doc.powerdns.com/authoritative/backends/generic-sql.html#generic-sql-handling-dnssec-signed-zones
"In addition, PowerDNS fully supports empty non-terminals. If you have a
zone example.com, and a host a.b.c.example.com in it, rectif
Anyone has some other ideas how to troubleshoot this, or can confirm
that this is normal behavior in new 4.1.0.?
On 16.11.2017 15:36, Mislav | SysAdmin wrote:
Is this something new by default in 4.1.0? We don't have DNSSEC
enabled in old environment, if this is DNSSEC related.
On 16.11.2017
Is this something new by default in 4.1.0? We don't have DNSSEC enabled
in old environment, if this is DNSSEC related.
On 16.11.2017 15:25, David wrote:
On 2017-11-16 2:07 AM, Mislav | SysAdmin wrote:
Hi. I've the following setup:
1) pdns server version 3.1 - with mysql backend
2) pdns server
On 2017-11-16 2:07 AM, Mislav | SysAdmin wrote:
Hi. I've the following setup:
1) pdns server version 3.1 - with mysql backend
2) pdns server version 4.1.0 - with mysql backend
What I'm trying to do is:
- replace version 3.1 with 4.1.0 and I've installed clean version of
4.1.0 to a new server and
Hi. I've the following setup:
1) pdns server version 3.1 - with mysql backend
2) pdns server version 4.1.0 - with mysql backend
What I'm trying to do is:
- replace version 3.1 with 4.1.0 and I've installed clean version of
4.1.0 to a new server and I'm trying to this this now:
https://doc.power
