Hi herbe, I can't comment on the pdns.local.gmysql fix that you found - I'll leave that to others.
Personally I would only use the instructions found on the developer's web site when fault finding. You could improve your dig statement perhaps: dig example.com all tells dig to query using your system's resolvers (found in /etc/resolv.conf most likely) which aren't necessarily going to query your new PowerDNS server immediately. If my IP address is 172.16.1.2 I'd use: dig @172.16.1.2 example.com all or similar to be certain PowerDNS is listening on the correct IP address / interface. Welcome to PowerDNS! :-) -- Kind Regards, Mark Homoky, IT Consultant. On 12/03/2014 08:54, herbe wrote: > Good day! > Now PowerDNS server is working. > Problem was, that pdns-backend-mysql package creates pdns database and > pdns.local.gmysql configuration file, that links to that database. > I don't know if it is good, but deleting pdns.local.gmysql file solves the > problem. Real database was described in pdns.local file. > > Thanx :) > > > > -- > View this message in context: > http://powerdns.13854.n7.nabble.com/PowerDNS-with-MySQL-backend-and-Poweradmin-on-Debian-Wheezy-tp10622p10623.html > Sent from the PowerDNS mailing list archive at Nabble.com. > > _______________________________________________ > Pdns-users mailing list > [email protected] > http://mailman.powerdns.com/mailman/listinfo/pdns-users
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Pdns-users mailing list [email protected] http://mailman.powerdns.com/mailman/listinfo/pdns-users
