gitzone

commit 07abc804138776b2bcfa291b168a72cfafbf0592
parent 1a1aa69b40186ec82dbbf6a67c99bbe1de889551
Author: tg(x) <*@tg-x.net>
Date:   Sat,  5 Feb 2011 17:23:36 +0100

docs

Diffstat:
M
README.org
 | 
22
++++++++++++++++++----

1 file changed, 18 insertions(+), 4 deletions(-)
diff --git a/README.org b/README.org
@@ -1,7 +1,7 @@
 #+TITLE: gitzone
 #+AUTHOR: tg(x)
 #+OPTIONS: ^:{}
-#+INFOJS_OPT: view:showall
+#+INFOJS_OPT: view:showall ltoc:nil
 
 * About
 
@@ -81,9 +81,10 @@ There are a few keywords you can use in the zone files:
 
 ** Git repository
 
-You can use the git repository as normal, only difference is that if you use the
-auto increment feature you also need to pull after a push as the receive hooks
-on the server make commits to the repository during a push.
+To make changes to the zones you need to clone the git repository, edit the
+files, commit the changes and finally push the changes to the server.  If you
+use the auto increment feature you also need to pull after a push as the receive
+hooks on the server make commits to the repository during a push.
 
 #+BEGIN_EXAMPLE
   % git clone ns.example.net:zones
@@ -108,3 +109,16 @@ The following SSH commands can be used:
   : % ssh ns.example.net add-key 'command="update-record example.net somehost IN A"' `cat id_rsa.pub`
 - =del-key=: delete an ssh key from the config
   : % ssh ns.example.net del-key user@somewhere
+
+** Dynamic DNS
+
+In order to do automatic dynamic DNS updates, create an SSH key without a
+password and use the add-key command to add it with a command= parameter which
+has an update-record command in it, see the example in the previous
+section. This way the host doing the updates does not have access to the git
+repository as it is restricted to the specified command only. Then all you have to do to
+update your IP is:
+: % ssh ns.example.net
+
+Run this command whenever the IP changes or the interface comes up. On
+Debian-like systems you can use a post-up command in /etc/network/interfaces.