Merge pull request #1831 from LLeny/master

Namecheap API

diff --cc dnsapi/README.md
index c8207b970821da4e2d3995d59481b90912750f3a,1421cc23bb396a999b82897f594bb520cc9cbdb6..2cecfa5a89a001749a83a6717c2df4e9299b7c9c
--- 1/dnsapi/README.md
--- 2/dnsapi/README.md
+++ b/dnsapi/README.md
@@@ -986,13 -986,31 +986,34 @@@ The username and password will be save
  
  Now you can issue a certificate.
  
 +Note: It usually takes a few minutes (usually 3-4 minutes) before the changes propagates to gratisdns.dk nameservers (ns3.gratisdns.dk often are slow),
 +and in rare cases I have seen over 5 minutes before google DNS catches it. Therefor a DNS sleep of at least 300 seconds are recommended-
 +
  ```sh
 -acme.sh --issue --dns dns_gdnsdk -d example.com -d *.example.com
 +acme.sh --issue --dns dns_gdnsdk --dnssleep 300 -d example.com -d *.example.com
  ```
  
+ ## 53. Use Namecheap
+ 
+ You will need your namecheap username, API KEY (https://www.namecheap.com/support/api/intro.aspx) and your external IP address (or an URL to get it), this IP will need to be whitelisted at Namecheap.
+ Due to Namecheap's API limitation all the records of your domain will be read and re applied, make sure to have a backup of your records you could apply if any issue would arise.
+ 
+ ```sh
+ export NAMECHEAP_USERNAME="..."
+ export NAMECHEAP_API_KEY="..."
+ export NAMECHEAP_SOURCEIP="..."
+ ```
+ 
+ NAMECHEAP_SOURCEIP can either be an IP address or an URL to provide it (e.g. https://ifconfig.co/ip).
+ 
+ The username and password will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
+ 
+ Now you can issue a certificate.
+ 
+ ```sh
+ acme.sh --issue --dns dns_namecheap -d example.com -d *.example.com
+ ```
+ 
  # Use custom API
  
  If your API is not supported yet, you can write your own DNS API.