[Pdns-users] How to log mysql query details

2018-12-21 Thread Cliff Hayes
I have the following in pdns.conf... launch=gmysql log-dns-details=yes logging-facility=0 loglevel=9 query-logging=yes ...but in the log the queries show question marks instead of values... pdns[18975]: Query: SELECT content,ttl,prio,type,domain_id,disabled,name,auth FROM records WHERE disabl

Re: [Pdns-users] errno - 128 with mysql

2018-12-21 Thread Cliff Hayes
I was already familiar with that link. The two solutions do not replicate the original setup of first looking at a local database then passing unresolved requests to another DNS server. On 12/21/2018 9:07 AM, Remi Gacogne wrote: On 12/21/18 3:56 PM, Cliff Hayes wrote: I have to use 4.0.6 beca

Re: [Pdns-users] errno - 128 with mysql

2018-12-21 Thread Remi Gacogne
On 12/21/18 3:56 PM, Cliff Hayes wrote: > I have to use 4.0.6 because authoritative + recursion was removed with 4.1. I'm sorry to insist, but I really think you should consider the following solutions to migrate to 4.1.0: https://docs.powerdns.com/authoritative/guides/recursion.html We don't in

Re: [Pdns-users] errno - 128 with mysql

2018-12-21 Thread Cliff Hayes
I have to use 4.0.6 because authoritative + recursion was removed with 4.1. I took your advice and ran the queries with the u/p used by pdns. I can see that errno 128 means the field is blank. In my pdns records table, the prio and auth fields are blank. So to fix, should I put a 10 in all of the

Re: [Pdns-users] errno - 128 with mysql

2018-12-21 Thread frank+pdns--- via Pdns-users
Hi Cliff, Besides the question about 4.0 vs 4.1 that Remi brought up, MySQL errno 128 can mean a few things. Could you try to issues those MySQL queries by hand, when connecting with the exact same user/password that PowerDNS uses to connect? Frank Louwers Certified PowerDNS Consultant > On

Re: [Pdns-users] errno - 128 with mysql

2018-12-21 Thread Remi Gacogne
Hi, On 12/20/18 7:25 PM, Cliff Hayes wrote: > I have just successfully installed authoritative server 4.0.6 on Fedora > 28.  It appears proper results are being returned on DNS queries but I > and am now seeing the following errors which are new to me.  I tried > putting in 2018122001 for all reco