From: Kees Monshouwer Date: Mon, 10 Mar 2014 08:29:49 +0000 (+0100) Subject: remove old schema from doc X-Git-Tag: rec-3.6.0-rc1~75^2~3 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=895df412645feea106cd63e810bac5ef0b9ef888;p=thirdparty%2Fpdns.git remove old schema from doc --- diff --git a/pdns/docs/pdns.xml b/pdns/docs/pdns.xml index e0e33a679c..1a65d4c9ad 100644 --- a/pdns/docs/pdns.xml +++ b/pdns/docs/pdns.xml @@ -11482,7 +11482,7 @@ name IN A 192.0.2.4 Example: configuring MySQL Connect to MySQL as a user with sufficient privileges and issue the following commands: - + Now we have a database and an empty table. PDNS should now be able to launch in monitor mode and display no errors: @@ -17699,15 +17699,11 @@ authoritative). The default setup conforms to the following schema: - + Zone2sql with the --gmysql flag also assumes this layout is in place. - - To support or migrate to DNSSEC, the following SQL statements must be executed: - - For full migration notes, please see . @@ -17734,7 +17730,7 @@ REFERENCES `domains` (`id`) ON DELETE CASCADE; PostgreSQL specifics The default setup conforms to the following schema, which you should add to a PostgreSQL database. - + Zone2sql with the --gpgsql flag also assumes this layout is in place. @@ -17742,10 +17738,6 @@ REFERENCES `domains` (`id`) ON DELETE CASCADE; This schema contains all elements needed for master, slave and superslave operation. - - To support DNSSEC or to migrate to DNSSEC, the following statements have to be issued: - - For full migration notes, please see . @@ -19290,20 +19282,11 @@ VALUES (:zoneid, :ip) Before you can use this backend you first have to set it up and fill it with data. The default setup conforms to the following schema: - + This schema contains all elements needed for master, slave and superslave operation. - - To support DNSSEC, or to migrate to DNSSEC, the following statements must be issued: - - - - - - For full migration notes, please see . - After you have created the database you probably want to fill it with data. If you have a BIND zone file it's as easy as: zone2sql --zone=myzonefile --gmysql | sqlite powerdns.sqlite, but