Is PowerDNS version 4 supported in ISPconfig 3?

Discussion in 'General' started by pvanthony, Jul 19, 2017.

  1. pvanthony

    pvanthony Member

    I know PowerDNS version 3 is supported and working with ISPconfig 3.
    Because of the CAA record requirement for letsencrypt certs, I was wondering if PowerDNS version 4 is supported with ISPconfig 3.
    Any advice?
  2. Jesse Norell

    Jesse Norell Well-Known Member

    I believe there are no PowerDNS versions currently supported, though it seems like someone recently was using one with old code/plugin. I believe CAA records will be supported soon, maybe in the next release? (@florian030 had mentioned it recently)
  3. pvanthony

    pvanthony Member

    While testing out PowerDNS version 3 and version 4 with ispconfig 3 on centos 6 and 7, there were some issues with the mysql database. I have made some modifications to the database. With the modified sql statements, it seems to work.
    Of course the full support of PowerDNS version 4 is currently not there. As for PowerDNS version 3, it seems to be there and working great.
    Here are the modified sql statements to create the powerdns database. These seem to work.

    ---------------- start of sql for creating powerdns database -------------------
    CREATE TABLE `domains` (
    `id` int(11) NOT NULL auto_increment,
    `name` varchar(255) NOT NULL,
    `master` varchar(128) default NULL,
    `last_check` int(11) default NULL,
    `type` varchar(6) NOT NULL,
    `notified_serial` int(11) default NULL,
    `account` varchar(40) default NULL,
    `ispconfig_id` int(11) NOT NULL,
    PRIMARY KEY (`id`)

    CREATE UNIQUE INDEX name_index ON domains(name);

    CREATE TABLE `records` (
    `id` int(11) NOT NULL auto_increment,
    `domain_id` int(11) default NULL,
    `name` varchar(255) default NULL,
    `type` varchar(6) default NULL,
    `content` varchar(255) default NULL,
    `ttl` int(11) default NULL,
    `prio` int(11) default NULL,
    `change_date` int(11) default NULL,
    `disabled` TINYINT(1) DEFAULT 0,
    `ordername` VARCHAR(255) BINARY DEFAULT NULL,
    `auth` TINYINT(1) DEFAULT 1,
    `ispconfig_id` int(11) NOT NULL,
    PRIMARY KEY (`id`)

    CREATE INDEX rec_name_index ON records(name);
    CREATE INDEX nametype_index ON records(name,type);
    CREATE INDEX domain_id ON records(domain_id);
    CREATE INDEX recordorder ON records (domain_id, ordername);

    CREATE TABLE `supermasters` (
    `ip` varchar(25) NOT NULL,
    `nameserver` varchar(255) NOT NULL,
    `account` varchar(40) default NULL

    CREATE TABLE domainmetadata (
    domain_id INT NOT NULL,
    kind VARCHAR(32),
    content TEXT,
    PRIMARY KEY (id)
    ) Engine=InnoDB DEFAULT CHARSET=utf8;

    CREATE INDEX domainmetadata_idx ON domainmetadata (domain_id, kind);
    ------------------------------------- end ----------------------------------------------
    till likes this.
  4. pvanthony

    pvanthony Member

    Tried searching the forums but could not find any comment on PowerDNS version 4 for ISPconfig 3.
    Hoping the developers would comment on it.
    Would PowerDNS version 4 be supported for ISPconfig version 3?
    Hope to hear some comments.
  5. till

    till Super Moderator Staff Member ISPConfig Developer

    There is no maintainer for the PowerDNS plugin, so PowerDNS is not supported in ISPConfig 3.1 at all, no matter which pdns version, until we find someone who likes to actively maintain the plugin again.

    So if you have some php knowledge and want to maintain the powerdns plugin code and keep it compatible with ISPConfig, then please let me know.
  6. pvanthony

    pvanthony Member

    Thank you for the reply. Just the information I needed.
    Unfortunately I am not good at programming.
    Looks like I may have to move to bind or sponsor the development. Not sure how much it is going to cost.
    I will message Till directly.
    Once again thank you for the reply.
    till likes this.
  7. ISPConfig Developer ISPConfig Developer

    hmm good idea, never used ISPConfig DNS b/c it states it likes bind all over the place, was about to move my external DNS from pdns to knot dns out of curiosity but... uhm integrating things ... @till how bad is the plugin? can't imagine it should be too hard to fix an existing base, but yeah I have no idea what changed - just curious
  8. pvanthony

    pvanthony Member

    That would be so cool if you can help. I really like pdns. Any reason for moving out of pdns?
  9. till

    till Super Moderator Staff Member ISPConfig Developer

    I guess the plugin is generally fine, needs just some adjustments and testing. But I don't use PowerDNS at all, so I can't say what has been changed. Also, there are probably functions missing that have been added in ISPConfig in the past few years as the plugin is unmaintained for a long time.
  10. ISPConfig Developer ISPConfig Developer

    looked at it, 2 years but as looking over the code nd seeing original author I'm confident it shouldn't be a pain to get it going sooner or later, don't stop looking, all I say is that I may! play a little bit with it at "home" ;)

    hmm changing to knot dns uhm no specific reasons, it has less features but I wonder wether it actually performs better as they're claiming ^^ even it's in a range I'll only reach when someone sends something named after an old PC-operating system which has a Free-version 1.something aswell ^^

    yeah I might stick with pdns
  11. pvanthony

    pvanthony Member

    Just curious. Got any chance to look at the code? Any chance of an upgrade that will support powerdns 4. Just asking. If no time, it's ok.

Share This Page