X-Git-Url: http://www.average.org/gitweb/?p=pdns-pipe-nmc.git;a=blobdiff_plain;f=README.md;fp=README.md;h=802ca9bc536daf1d9221c0ee0f8b19d78b0a325b;hp=2cf634d805b2784c47ca1a60c3a7b87914ab5c83;hb=28028363f33b8ec698b114c65b2a858d7ea34c15;hpb=d77bb5ba5f562ca2d83110b9ca5e7ff7bead185a

diff --git a/README.md b/README.md
index 2cf634d..802ca9b 100644
--- a/README.md
+++ b/README.md
@@ -54,7 +54,10 @@ rpcport=8336
 
 They are the parameters needed to contact the `namecoind` server over
 its JsonRPC interface. With default installation on `localhost`, you
-will only need to specify `password`.
+will only need to specify `rpcpassword`.
+
+Configure your resolvers to use the PowerDns instance for queries in
+the `.bit` zone. This is left as an exercise to the reader.
 
 ## Security Considerations
 
@@ -66,7 +69,7 @@ hackers or ruthless governments from tampering with your queries
 and powerdns responses. There are two possible approaches to
 mitigation of this problem:
 
-* Run `namecoind` and the bridge as close to the consumer as
+* Run namecoind and powerdns as close to the consumer as
 possible: on the same host, or at least on the same network, and
 keep it guarded.
 * I did not try it, but it should be possible to use PowerDNS