2. From PowerDNS Authoritative Server 3.0 to 3.1

[Note]Note

If you are coming from 2.9.x, please also read Section 1, “From PowerDNS Authoritative Server 2.9.x to 3.0”.

PowerDNS 3.1 introduces native SQLite3 support for storing key material for DNSSEC in the bindbackend. With this change, support for bind+gsql-setups ('hybrid mode') has been dropped. If you were using this mode, you will need to switch to bind-dnssec-db and migrate your keying material.

There have been changes to the SQL schemas for the generic backends.

For MySQL:

    		mysql> ALTER TABLE records MODIFY content VARCHAR(64000);
    		mysql> ALTER TABLE tsigkeys MODIFY algorithm VARCHAR(50);
    	

The definition of 'auth' and 'ordername' in backends has changed slightly, see Section 8.5, “Rules for filling out fields in database backends”.

PowerDNS 3.0 and 3.1 will only fetch DNSSEC metadata and key material from the first DNSSEC-capable backend in the launch line. In 3.1, the bindbackend supports DNSSEC storage. This means that setups using launch=bind,gsqlite3 or launch=gsqlite3,bind may break. Please tread carefully!