Merge pull request #77 from germeier/master

add support for dns-01 challenge - try 2

diff --cc README.md
index 3457525bd518318596f744f2c30db7aafea5cec5,d8774e62f8baf8f69853bb1c7a2b375b163b8fdc..594ddd4b0f05eceeeeb779b558aed956aa9b198f
--- 1/README.md
--- 2/README.md
+++ b/README.md
@@@ -76,6 -80,28 +77,12 @@@ WELLKNOWN="/var/www/letsencrypt
  An alternative to setting the WELLKNOWN variable would be to create a symlink to the default location next to the script (or BASEDIR):
  `ln -s /var/www/letsencrypt .acme-challenges`
  
+ ### dns-01 challenge
+ 
+ This script also supports the new `dns-01`-type verification. Be aware that at the moment this is not available on the production servers from letsencrypt. Please read `https://community.letsencrypt.org/t/dns-challenge-is-in-staging/8322` for the current state of `dns-01` support.
+ 
+ You need a hook script that deploys the challenge to your DNS server!
+ 
  ## Import
  
 -### import-account.pl
 -
 -This perl-script can be used to import the account key from the original letsencrypt client.
 -
 -You should copy `private_key.json` to the same directory as the script.
 -The json-file can be found in a subdirectory of `/etc/letsencrypt/accounts/acme-v01.api.letsencrypt.org/directory`.
 -
 -Usage: `./import-account.pl`
 -
 -### import-certs.sh
 -
 -This script can be used to import private keys and certificates created by the original letsencrypt client.
 -
 -By default it expects the certificates to be found under `/etc/letsencrypt`, which is the default output directory of the original client.
 -You can change the path by setting LETSENCRYPT in your config file: ```LETSENCRYPT="/etc/letsencrypt"```.
 -
 -Usage: `./import-certs.sh`
 +If you want to import existing keys from the official letsencrypt client have a look at [Import from official letsencrypt client](https://github.com/lukas2511/letsencrypt.sh/wiki/Import-from-official-letsencrypt-client).

diff --cc letsencrypt.sh
Simple merge