On Fri, May 1, 2015 at 11:50 AM, bert hubert bert.hub...@powerdns.com
wrote:
On Fri, May 01, 2015 at 11:13:22AM -0700, Mark Moseley wrote:
Of all the things I cleaned up, one thing I *didn't* clean up a lot of
records with trailing dots in the content field (for NS/MX/CNAME
records).
This
This is going to be necessarily vague because I'm not even 50% sure what's
going on. Setup is Ubuntu Precise 64-bit, temporarily running 3.4.4. We
were (and are) running 3.4.2 previously. The scenario below was painful
enough that we didn't try 3.4.3 yet, but we can.
We've got a pretty big
On Fri, May 1, 2015 at 11:24 AM, Aki Tuomi cmo...@youzen.ext.b2.fi wrote:
On Fri, May 01, 2015 at 11:13:22AM -0700, Mark Moseley wrote:
This is going to be necessarily vague because I'm not even 50% sure
what's
going on. Setup is Ubuntu Precise 64-bit, temporarily running 3.4.4. We
were
On Fri, May 01, 2015 at 11:13:22AM -0700, Mark Moseley wrote:
This is going to be necessarily vague because I'm not even 50% sure what's
going on. Setup is Ubuntu Precise 64-bit, temporarily running 3.4.4. We
were (and are) running 3.4.2 previously. The scenario below was painful
enough that
On Fri, May 01, 2015 at 11:13:22AM -0700, Mark Moseley wrote:
Of all the things I cleaned up, one thing I *didn't* clean up a lot of
records with trailing dots in the content field (for NS/MX/CNAME records).
This could easily confuse things. If PowerDNS chases a CNAME and it
encounters a
Hi everybody,
Last week, we released Security Advisory 2015-01
(https://doc.powerdns.com/md/security/powerdns-advisory-2015-01/), with text
suggesting that only specific platforms were seriously affected. We must now
report that this was incorrect: all platforms are impacted. The advisory has
