<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2. From PowerDNS Authoritative Server 3.0 to 3.1</title><link rel="stylesheet" href="docbook.css" type="text/css" /><meta name="generator" content="DocBook XSL Stylesheets V1.75.2" /><link rel="home" href="index.html" title="PowerDNS manual" /><link rel="up" href="upgrades.html" title="Chapter 11. Notes on upgrading" /><link rel="prev" href="upgrades.html" title="Chapter 11. Notes on upgrading" /><link rel="next" href="from3.1to3.2.html" title="3. From PowerDNS Authoritative Server 3.1 to 3.2" /></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">2. From PowerDNS Authoritative Server 3.0 to 3.1</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="upgrades.html">Prev</a> </td><th width="60%" align="center">Chapter 11. Notes on upgrading</th><td width="20%" align="right"> <a accesskey="n" href="from3.1to3.2.html">Next</a></td></tr></table><hr /></div><div class="sect1" title="2. From PowerDNS Authoritative Server 3.0 to 3.1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="from3.0to3.1"></a>2. From PowerDNS Authoritative Server 3.0 to 3.1</h2></div></div></div><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><table border="0" summary="Note"><tr><td rowspan="2" align="center" valign="top" width="25"><img alt="[Note]" src="note.png" /></td><th align="left">Note</th></tr><tr><td align="left" valign="top"><p>
If you are coming from 2.9.x, please also read <a class="xref" href="upgrades.html#from2.9to3.0" title="1. From PowerDNS Authoritative Server 2.9.x to 3.0">Section 1, “From PowerDNS Authoritative Server 2.9.x to 3.0”</a>.
</p></td></tr></table></div><p>
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.
</p><p>
There have been changes to the SQL schemas for the generic backends.
</p><p>
For MySQL:
</p><pre class="screen">
mysql> ALTER TABLE records MODIFY content VARCHAR(64000);
mysql> ALTER TABLE tsigkeys MODIFY algorithm VARCHAR(50);
</pre><p>
</p><p>
The definition of 'auth' and 'ordername' in backends has changed slightly, see <a class="xref" href="dnssec-modes.html#dnssec-direct-database" title="8.5. Rules for filling out fields in database backends">Section 8.5, “Rules for filling out fields in database backends”</a>.
</p><p>
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!
</p></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="upgrades.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="upgrades.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="from3.1to3.2.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 11. Notes on upgrading </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 3. From PowerDNS Authoritative Server 3.1 to 3.2</td></tr></table></div></body></html>
