Add some documentation regarding the new comand

diff --git a/docs/manpages/pdnsutil.1.rst b/docs/manpages/pdnsutil.1.rst
index b8a3baa596134429841dd8e86f28bdd453f309b1..f5a76d21cfe45b20f872125b19bb204b2491501b 100644 (file)
--- a/docs/manpages/pdnsutil.1.rst
+++ b/docs/manpages/pdnsutil.1.rst
@@ -160,6 +160,8 @@ ZONE MANIPULATION COMMANDS
 add-record *ZONE* *NAME* *TYPE* [*TTL*] *CONTENT*
     Add one or more records of *NAME* and *TYPE* to *ZONE* with *CONTENT* 
     and optional *TTL*. If *TTL* is not set, default will be used. 
+add-supermaster *IP* *NAMESERVER* [*ACCOUNT*]
+    Add a supermaster entry into the backend. This enables receiving zone updates from other servers.
 create-zone *ZONE*
     Create an empty zone named *ZONE*.
 create-slave-zone *ZONE* *MASTER* [*MASTER*]..

diff --git a/docs/modes-of-operation.rst b/docs/modes-of-operation.rst
index d2f6aabe07059f7787eed13ad478da15983b5394..ff891db5b92796920bc0f43b16269e201f7b7b88 100644 (file)
--- a/docs/modes-of-operation.rst
+++ b/docs/modes-of-operation.rst
@@ -222,7 +222,9 @@ So, to benefit from this feature, a backend needs to know about the IP
 address of the supermaster, and how PowerDNS will be listed in the set
 of NS records remotely, and the 'account' name of your supermaster.
 There is no need to fill the account name out but it does help keep
-track of where a domain comes from.
+track of where a domain comes from. 
+Adding a supermaster can be done either directly in the database,
+or by using the 'pdnsutil add-supermaster' command. 
 
 .. note::
   Removal of zones provisioned using the supermaster must be