Ok, just did
On Mon, Mar 2, 2015 at 2:04 AM, Peter van Dijk
wrote:
> Hello Mark,
>
> On 28 Feb 2015, at 0:09 , Mark Moseley 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
Hello Mark,
On 28 Feb 2015, at 0:09 , Mark Moseley 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 from the config a
On Fri, Feb 27, 2015 at 2:18 PM, bert hubert
wrote:
> On Fri, Feb 27, 2015 at 02:15:12PM -0800, Mark Moseley wrote:
> > We don't do a lot (or practically any) AXFRs, so I hadn't noticed this
> > before now.
>
> Hi Mark,
>
> You probably have something in the database that upsets us (which should
On Fri, Feb 27, 2015 at 02:15:12PM -0800, Mark Moseley wrote:
> We don't do a lot (or practically any) AXFRs, so I hadn't noticed this
> before now.
Hi Mark,
You probably have something in the database that upsets us (which should not
happen of course).
Can you run pdnssec check-zone on example2
We don't do a lot (or practically any) AXFRs, so I hadn't noticed this
before now.
For every domain of ours that I've tried, doing an AXFR (to a pdns running
on localhost -- mysqld running on localhost too; running the powerdns
ubuntu precise package for 3.4.2, not running dnssec), it appears to c
