From: Pieter Lexis <pieter.lexis@powerdns.com>
Date: Tue, 20 Dec 2016 17:49:54 +0000 (+0100)
Subject: Describe more migration methods
X-Git-Tag: rec-4.1.0-alpha1~349^2~2
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=24e1aae70c0d7a02c366062530ea5bbc9a9426f7;p=thirdparty%2Fpdns.git

Describe more migration methods
---

diff --git a/docs/markdown/authoritative/migration.md b/docs/markdown/authoritative/migration.md
index e7ec5114d0..4d7194e847 100644
--- a/docs/markdown/authoritative/migration.md
+++ b/docs/markdown/authoritative/migration.md
@@ -101,6 +101,12 @@ zone2sql --named-conf=/path/to/named.conf --gmysql | mysql -u pdns -p pdns-db
 This will generate the SQL statements for the [Generic MySQL](backend-generic-mysql.md)
 and pipe them into the pdns-db database in MySQL.
 
+### Using `pdnsutil load-zone`
+The [`pdnsutil`](../manpages/pdnsutil.1.md) tool has a `load-zone` command that ingests a zone file and imports it into the first backend that is capable of hosting it.
+
+To import, configure the backend and run `pdnsutil load-zone example.com /tmp/example.com.com.zone` to import 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.
+
 # Migrating Data from one Backend to Another Backend
 NB! This is experimental feature.