[Pdns-users] strange behaviour with gmysql & mydns backend

[Andreas Danzer]

Hi,

I'm running powerdns-server 3.3.1 with gmysql and mydns backend enabled
simultaneously (launch=gmysql,mydns). I'd like to setup new zones in the
gmysql backend, while my old zones stay in the mydns backend until I'm
able to transfer them to the native gmysql backend. Zones in the mydns
backend work without a problem. If I want to look up A records for zones
in the gmysql backend - SOA, NS, MX, ANY work - I get backend errors. It
looks like the query is getting the correct ZoneID but then fails.

example:

The zone danzer-test.de is in the gmysql-backend database. A "dig
@dns.mydns.de A www.danzer-test.de" results in following logfile entries:

Query: select content,ttl,prio,type,domain_id,name from records where
type='SOA' and name='danzer-test.de'
Jan 17 16:36:41 1371476707-1 pdns[28287]: Query: select
content,ttl,prio,type,domain_id,name from records where type='NS' and
name='www.danzer-test.de' and domain_id=50000002
Jan 17 16:36:41 1371476707-1 pdns[28287]: Query: select origin, minimum
from soa where id = 50000002 and active = 1 and 1 = 1
Jan 17 16:36:41 1371476707-1 pdns[28287]: Backend reported permanent
error which prevented lookup (lookup() passed zoneId = 50000002 but no
such zone!) sending out servfail
Jan 17 16:36:41 1371476707-1 pdns[28287]: Backend error: lookup() passed
zoneId = 50000002 but no such zone!
Jan 17 16:36:45 1371476707-1 pdns[28287]: Engaging bypass - now
operating unthreaded

A "dig @dns.mydns.de ANY danzer-test.de" works.

If I disable the mydns backend, gmysql works without a problem.
Transfering the zone from the mydns backend to gmysql is not an option
at the moment as several systems depend on the old structure.

Has anybody been able to get a similar setup to work without problems?
Is there a workaround?

Best regards,
Andreas