MyDNS can be migrated with b2b-migrate

diff --git a/docs/backends/mydns.rst b/docs/backends/mydns.rst
index 28a5a35e04dd0d6607760080441de9173d2535d7..ee9fcc178c43dbc2c2e848eb1e92c39cf9328e11 100644 (file)
--- 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 <generic-sql>`, like the :doc:`Postgresql <generic-postgresql>` or :doc:`MySQL <generic-mysql>` backends, the data can be migratedusing the :ref:`Backend to Backend <b2b-migrate>` migration guide.

diff --git a/docs/migration.rst b/docs/migration.rst
index 78f60cdf8a4074ff0880dff61aadf6c9956f26af..653a42c144b01b5627217b404fa6949cf5f18d56 100644 (file)
--- 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
 --------------------------------------------------