Updates documentation for addDomainKey, pdnsutil

diff --git a/docs/manpages/pdnsutil.1.md b/docs/manpages/pdnsutil.1.md
index 3e2f5d231c1c237e674d458a9147809b9d1b606d..535d1fb17dd15addfe14d320a1d7d6ace05de966 100644 (file)
--- a/docs/manpages/pdnsutil.1.md
+++ b/docs/manpages/pdnsutil.1.md
@@ -52,7 +52,7 @@ activate-zone-key *ZONE* *KEY-ID*
 add-zone-key *ZONE* {**KSK**,**ZSK**} [**active**,**inactive**] *KEYBITS* *ALGORITHM*
 :   Create a new key for zone *ZONE*, and make it a KSK or a ZSK, with the
     specified algorithm. The key is inactive by default, set it to **active** to
-    immediately use it to sign *ZONE*.
+    immediately use it to sign *ZONE*. Prints the id of the added key.
 
 create-bind-db *FILE*
 :    Create DNSSEC database (sqlite3) at *FILE* for the BIND backend.
@@ -80,7 +80,7 @@ generate-zone-key {**KSK**,**ZSK**} [*ALGORITHM*] [*KEYBITS*]
 import-zone-key *ZONE* *FILE* {**KSK**,**ZSK**}
 :    Import from *FILE* a full (private) key for zone called *ZONE*. The format
      used is compatible with BIND and NSD/LDNS. **KSK** or **ZSK** specifies the
-     flags this key should have on import.
+     flags this key should have on import. Prints the id of the added key.
 
 remove-zone-key *ZONE* *KEY-ID*
 :    Remove a key with id *KEY-ID* from a zone called *ZONE*.

diff --git a/docs/markdown/authoritative/backend-remote.md b/docs/markdown/authoritative/backend-remote.md
index bedaaf72e14684a5c2986be1a0681710a83427de..f92314ff357f87ca95cf076e73ef2fba8dd4dcc9 100644 (file)
--- a/docs/markdown/authoritative/backend-remote.md
+++ b/docs/markdown/authoritative/backend-remote.md
@@ -370,7 +370,7 @@ Adds key into local storage. See [`getDomainKeys`](#getdomainkeys) for more info
 
 * Mandatory: No
 * Parameters: name, key=`<flags,active,content>`
-* Reply: true for success, false for failure
+* Reply: id (>= 0) for success, -1 for failure
 
 #### Example JSON/RPC
 Query: