Peter van Dijk wrote:
(2) it looks like your RRSIGs and KSK DNSKEY on the slave are truncated; we
recommend increasing the size of the ‘content’ column in the records table
(see our upgrade notes https://doc.powerdns.com/md/authoritative/upgrading/
)
(Sigh!) I really wonder why the LDAP
Hello Mark,
On 28 Feb 2015, at 0:09 , Mark Moseley moseleym...@gmail.com wrote:
It's actually more likely I'm an idiot.
I forgot to remove a custom 'gmysql-list-query' query from when I was trying
to make pdns 3.4 work with the 2.9.x schema (and gave up -- but forgot to
remove the query
Hello Nick,
On 27 Feb 2015, at 19:27 , Nick Williams nicho...@nicholaswilliams.net wrote:
I've recently enabled DNSSEC with the MySQL backend. I'm using the MySQL
Backend for everything (including storage of zones/records). If I remove a
zone completely from the MySQL domains/records tables
Hoi Maurice,
On 27 Feb 2015, at 9:44 , Maurice Sienema msien...@unet.nl wrote:
We are testing with DNSSEC on our PowerDNS setup, everything seems to be
working except the slave server isn't using the DNSKEY set from the master,
am I missing the concept and should I register both keys at the
Hi everybody,
We're pleased to announce the immediate availability of the PowerDNS
Authoritative Server version 3.4.3. This release is an iteration over
3.4.2, mainly fixing small issues, correcting wrong behavior in tools
and adding work to the experimental API.
One major change is the fact we
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi everybody,
With this message, I'd like to congratulate our newest employee Pieter for
doing a PowerDNS release on his first day of work!
Even though the trains failed massively this morning in The Netherlands, it
all worked out.
Welcome to the
Hello,
I would like to ask for your experience and advice on the following
situation:
When we use a private IPv4 subnet (e.g. 10.10.10.0/24) with NAT (to
access the Internet) and at the same time (i.e. on the same LAN or
VLAN) we use a public IPv6 address
