Re: [Pdns-users] strange servfail

As far as I know this issue has been solved for now. The custom query for the cryptokeys returned a few rows even for domains that were not in the backend (we use one set of keys for all our domains so the query didn't use a domain filter at all in the WHERE clause). I guess in the older

Re: [Pdns-users] strange servfail

Yes, but I have checked and double checked all custom queries, and all fields in the SELECT clauses are in the correct order (correct = order of fields as in the Powerdns source code queries). I have no idea where that malformed type is coming from. When I disable the backend with the custom

Re: [Pdns-users] strange servfail

Can you show your custom queries? Aki On Sun, Nov 01, 2015 at 03:41:41PM +0100, Martin wrote: > Yes, but I have checked and double checked all custom queries, and > all fields in the SELECT clauses are in the correct order (correct = > order of fields as in the Powerdns source code queries). I

[Pdns-users] strange servfail

Hi, I have setup a simple MySQL backend for a domain with a few MX records, a couple of A records, two NS records and a SOA record for the domain. All dig commands are run from a completely unrelated server: dig a www.example.com is working: it returns the right A record dig a

Re: [Pdns-users] strange servfail

Hi Martin, You appear to have put domain names in the type field! The error messages say the type is example.example.com. Bert On Oct 29, 2015 17:10, Martin wrote: > > Hi, > > I have setup a simple MySQL backend for a domain with a few MX records, a > couple of A

Re: [Pdns-users] strange servfail

Is it possible for you to provide actual data? Also, - have you turned on dnssec support? gmysql-dnssec=yes - can you provide the actual line(s) from mysql database - can you run pdnssec check-zone zone Aki On Thu, Oct 29, 2015 at 08:18:29PM +0100, Martin wrote: > > > Hi, > > Thanks for

Re: [Pdns-users] strange servfail

No, except for the aforementioned ' unknown dns type 'hoofdluis.hoofdluis.nl' ' message which is probably why the queries fail but I am unable to track down where this error is coming from. I'm guessing Powerdns tries to build a query and decided something is wrong, but since it is never