From: Pieter Lexis Date: Mon, 6 Nov 2017 18:15:31 +0000 (+0100) Subject: MyDNS can be migrated with b2b-migrate X-Git-Tag: auth-4.1.0~13^2~1 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=f284956d685dada2beaf226137219aefc96c0178;p=pdns MyDNS can be migrated with b2b-migrate --- diff --git a/docs/backends/mydns.rst b/docs/backends/mydns.rst index 28a5a35e0..ee9fcc178 100644 --- a/docs/backends/mydns.rst +++ b/docs/backends/mydns.rst @@ -112,3 +112,7 @@ Use the active column in the resource record table, "yes" by default. Setting this to 'yes' will make the backend behave like MyDNS on the TTL values. Setting it to 'no' will make it ignore the minimal-ttl of the zone. The default is "yes". + +Migrating from MyDNS to another SQL backend +------------------------------------------- +To use one of the :doc:`generic SQL backend `, like the :doc:`Postgresql ` or :doc:`MySQL ` backends, the data can be migratedusing the :ref:`Backend to Backend ` migration guide. diff --git a/docs/migration.rst b/docs/migration.rst index 78f60cdf8..653a42c14 100644 --- a/docs/migration.rst +++ b/docs/migration.rst @@ -136,6 +136,8 @@ the ``example.com`` domain from the ``/tmp/example.com.zone`` file. The zone is imported atomically (i.e. it is fully imported, or not) and any existing records for that zone are overwritten. +.. _b2b-migrate: + Migrating Data from one Backend to Another Backend --------------------------------------------------