PDNS 4.0.0-alpha2 in Xenial is horribly broken(*) so IMO it seems a bit of a waste of effort backporting this specific fix, without also backporting the critical fixes from 4.0.0 alpha 3 and later, which in turn would be best done by going straight to 4.0.0 release (or 4.0.4+)
PDNS is a fine piece of software, and it's a shame that for many people their first experience will be using the Xenial package, which may put them off forever - it nearly did for me.
PDNS 4.0.0-alpha2 in Xenial is horribly broken(*) so IMO it seems a bit of a waste of effort backporting this specific fix, without also backporting the critical fixes from 4.0.0 alpha 3 and later, which in turn would be best done by going straight to 4.0.0 release (or 4.0.4+)
PDNS is a fine piece of software, and it's a shame that for many people their first experience will be using the Xenial package, which may put them off forever - it nearly did for me.
(*) at least with a SQL backend: /mailman. powerdns. com/pipermail/ pdns-users/ 2016-May/ 024192. html
https:/
At the moment, it seems the only safe way to run pdns-server on Xenial is to use the packages from the origin repository: https:/ /repo.powerdns. com/