From: shimmi2 Date: Mon, 9 Feb 2015 13:06:55 +0000 (+0100) Subject: Update migration.md X-Git-Tag: rec-3.7.0~2^2 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=04d481b51efd198162ebd0c716a35a8cd749f422;p=thirdparty%2Fpdns.git Update migration.md Updated link to wiki for easy reach scripts for migrating from MyDNS --- diff --git a/docs/markdown/authoritative/migration.md b/docs/markdown/authoritative/migration.md index 39b88dcf80..4f99ca24bf 100644 --- a/docs/markdown/authoritative/migration.md +++ b/docs/markdown/authoritative/migration.md @@ -4,7 +4,7 @@ Before migrating to PowerDNS a few things should be considered. PowerDNS does not operate as a 'slave' or 'master' server with all backends. Only the [Generic SQL](backend-generic-mypgsql.md), [BIND](backend-bind.md) backends have the ability to act as master or slave. -To migrate, the `zone2sql` tool is provided. +To migrate, the `zone2sql` tool is provided. There are also scripts from external contributors for migrating from `MyDNS` server. See https://github.com/PowerDNS/pdns/wiki/Migrating-DBs-FROM-MyDNS for details. Additionally, the PowerDNS source comes with a number of diagnostic tools, which can be helpful in verifying proper PowerDNS operation, versus incumbent nameservers. See [Tools to analyse DNS traffic](../tools/analysis.md) for more details.