No bind backend compiled in

[Igor A Tarasov]

The package contains the next in the description:

"... It also includes the bind backend that allows PowerDNS to retrieve domain info from zone files as used by the
 "bind" software."

But actually it does not.

root@nx9420:/etc/apt/sources.list.d# pdns_server --help=bind
Nov 24 00:21:32 Reading random entropy from '/dev/urandom'
syntax:

root@nx9420:/etc/apt/sources.list.d# pdns_server --help 2>&1| grep bind
 Local IP addresses to which we bind
 Local IP address to which we bind

/usr/share/doc/pdns-server/examples/pdns.local.bind contains the following options:
bind-example-zones
bind-config=/etc/bind/named.conf.local
bind-check-interval=
bind-enable-huffman

But I use it in config, pdns-server won't start because of unknown configuration directives.

Please, compile with internal bind backend.

[Peter van Dijk (habbie)]

The bindbackend is always compiled in. However, you need to say 'launch=bind' to activate it.

If this works for you, please close this ticket.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[John Edwards (john-cornerstonelinux)]

I have also met this problems on Ubuntu 12.04 with pdns-server and pdns-backend-mysql packages version 3.0-1.1ubuntu1.

PowerDNS was installed and worked with MySQL.

I then included a known good BIND configuration from another server to /etc/bind/named.conf.local . Then copied /usr/share/doc/pdns-server/examples/pdns.local.bind to /etc/powerdns/pdns.d/pdns.local.bind, added "launch=bind" and uncommented the "bind-example-zones" and "bind-config=/etc/bind/named.conf.local" lines.

Error messages from syslog:
Dec 17 18:22:34 ff0067 pdns[12709]: Listening on controlsocket in '/var/run/pdns.controlsocket'
Dec 17 18:22:34 ff0067 pdns[12711]: Guardian is launching an instance
Dec 17 18:22:34 ff0067 pdns[12711]: Reading random entropy from '/dev/urandom'
Dec 17 18:22:34 ff0067 pdns[12711]: This is module gmysqlbackend.so reporting
Dec 17 18:22:34 ff0067 pdns[12711]: This is a guarded instance of pdns
Dec 17 18:22:34 ff0067 pdns[12711]: Fatal error: Trying to set unexisting parameter 'bind-example-zones'
Dec 17 18:22:35 ff0067 pdns[12709]: Our pdns instance exited with code 1
Dec 17 18:22:35 ff0067 pdns[12709]: Respawning

I tried disabling the bind-example-zones options and got the message:
Fatal error: Trying to set unexisting parameter 'bind-config'
(bind-config being the next bind specific option in the /etc/powerdns/pdns.d/pdns.local.bind file)

I also tried moving the bind and launch options into /etc/powerdns/pdns.con, and disabling the MySQL configuration in /etc/powerdns/pdns.d/pdns.local.gmysql to make it a plain install. Neither seemed to make any difference.

[John Edwards (john-cornerstonelinux)]

Some more research leads to this PowerDNS bug:
  http://wiki.powerdns.com/trac/ticket/502

Which is mentioned in the NEWS.Debian.gz file in pdns 3.1 Debian packages, but not in the Ubuntu packages:
--------
  pdns now ships an empty, but activated bind backend so that the daemon
  can launch immediately. Since PowerDNS only allows a single launch
  statement (see http://wiki.powerdns.com/trac/ticket/502), you need to
  adapt either the new simplebind configuration or your custom
  configuration.

  PowerDNS will not flag multiple launch statements as an error, but it
  will only honor one of them. Be aware of that if your PowerDNS
  complains about configuration for a not enabled backend.
--------

Basically you can only have one "launch=" line anywhere in any of the PowerDNS configuration files, see:
http://doc.powerdns.com/pdns-users-faq.html

Perhaps this could be added to the documentation in the Ubuntu package?