Alberto, I spent 5 minutes copy pasting and setting up directories getting this to work. You also did not supply the other included files like .options, .local and .default-zones, so perhaps there is a problem in there I can't see.
Please understand that if you want free help from a free software product everything goes better if you deliver files in a way that is easy for the authors to work on and actually includes everything needed to see the problem. I found that zone2sql here has problems with this line: channel "querylog" { file "/var/log/bind9.log"; print-time yes; }; If you remove that, things appear to work fine. Zone2sql wouldn't do anything with the channel anyhow so it is no loss. Can you try? Bert > root@powerdns:/etc/bind# cat named.conf > > *// This is the primary configuration file for the BIND DNS server named. > // > // Please read /usr/share/doc/bind9/README.Debian.gz for information on the > // structure of BIND configuration files in Debian, *BEFORE* you customize > // this configuration file. > // > // If you are just adding zones, please do that in > /etc/bind/named.conf.local > > include "/etc/bind/named.conf.options"; > include "/etc/bind/named.conf.local"; > include "/etc/bind/named.conf.default-zones"; > include "/etc/bind/named.conf.dominios"; > > logging { > channel "querylog" { file "/var/log/bind9.log"; print-time yes; }; > category queries { querylog; }; > }; > > key "TRANSFER" { > algorithm hmac-md5; > secret "/REPLACEDFORCONFIDENCIALITY/=="; > }; > > server 192.168.25.158 { > keys { > TRANSFER; > }; > }; > > *# cat named.conf.dominios > * > zone "domainOne.es" { > type master; > file "/etc/bind/dominios/db.domainOne.es"; > also-notify {192.168.25.159;}; > allow-transfer {192.168.25.159;}; > }; > > zone "domainTwo.es" { > type master; > file "/etc/bind/dominios/db.domainTwo.es"; > also-notify {192.168.25.159;}; > allow-transfer {192.168.25.159;}; > }; > > zone "domainThree.es" { > type master; > file "/etc/bind/dominios/db.domainThree.es"; > also-notify {192.168.25.159;}; > allow-transfer {192.168.25.159;}; > }; > > zone "domainFour.es" { > type master; > file "/etc/bind/dominios/db.domainFour.es"; > also-notify {192.168.25.159;}; > allow-transfer {192.168.25.159;}; > }; > > *# cat dominios/db.domainOne.es > *$TTL 43200 > @ IN SOA ns1.mywork.es. sistemas.mywork.es. ( > 2016050203 ; Serial > 14400 ; Refresh > 1800 ; Retry > 1209600 ; Expire > 3600 ) ; Negative Cache TTL > ; > @ IN NS ns1.mywork.es. > @ IN NS ns2.mywork.es. > > @ IN MX 50 mail.domainOne.es. > @ IN TXT "v=spf1 a mx a:3948.submission.antispamcloud.com -all" > @ IN A 39.81.220.16 > www IN CNAME domainOne.es. > empleados IN A 39.81.220.16 > mail IN A 39.83.220.16 > pop3 IN CNAME mail.domainOne.es. > imap IN CNAME mail.domainOne.es. > smtp IN CNAME mail.domainOne.es. > webmail IN CNAME mail.domainOne.es. > @ IN MX 10 mx.spamexperts.com. > @ IN MX 20 fallbackmx.spamexperts.eu. > @ IN MX 30 astmx.spamexperts.net. > > > Best regards, and sorry for my english.* > > * > On 18/05/16 11:12, bert hubert wrote: > > On Wed, May 18, 2016 at 10:51:58AM +0200, @lbertosolorzano wrote: > >> Hi, > >> > >> At work are thinking to migrate our nsX servers to PowerDNS from bind, > >> all its ok, but when we went to use zone2sql show this error: > > Hi Alberto, > > > > Can you make an exact set of files that fails? So an named.conf & the > > included file named.conf.dominios. > > > > We don't want to have to work before we actually see your problem. > > > > So we need two files that fail for you and that will fail for us too. Then > > we can help you. > > > > Thanks! > > > > Bert > _______________________________________________ Pdns-users mailing list Pdns-users@mailman.powerdns.com https://mailman.powerdns.com/mailman/listinfo/pdns-users