Browse Source

Minor edits to FreeDNS documentation

cron
David Kerr 8 years ago
parent
commit
e6b940e247
  1. 2
      README.md
  2. 7
      dnsapi/README.md

2
README.md

@ -270,7 +270,7 @@ You don't have to do anything manually!
1. ISPConfig 3.1 API 1. ISPConfig 3.1 API
1. Alwaysdata.com API 1. Alwaysdata.com API
1. Linode.com API 1. Linode.com API
1. FreeDNS
1. FreeDNS (https://freedns.afraid.org/)
**More APIs coming soon...** **More APIs coming soon...**

7
dnsapi/README.md

@ -278,7 +278,7 @@ acme.sh --issue --dns dns_linode --dnssleep 900 -d example.com -d www.example.co
The `LINODE_API_KEY` will be saved in `~/.acme.sh/account.conf` and will be reused when needed. The `LINODE_API_KEY` will be saved in `~/.acme.sh/account.conf` and will be reused when needed.
## 15. Use FreeDNS
## 15. Use FreeDNS
FreeDNS (https://freedns.afraid.org/) does not provide an API to update DNS records (other than IPv4 and IPv6 FreeDNS (https://freedns.afraid.org/) does not provide an API to update DNS records (other than IPv4 and IPv6
dynamic DNS addresses). The acme.sh plugin therefore retrieves and updates domain TXT records by logging dynamic DNS addresses). The acme.sh plugin therefore retrieves and updates domain TXT records by logging
@ -298,12 +298,9 @@ reuses that when needed.
Now you can issue a certificate. Now you can issue a certificate.
```sh ```sh
acme.sh --issue --dns dns_freedns --dnssleep 30 -d example.com -d www.example.com
acme.sh --issue --dns dns_freedns -d example.com -d www.example.com
``` ```
FreeDNS updates records quite quickly so it is possible to reduce the dnssleep time, in the above example
to 30 seconds.
# Use custom API # Use custom API
If your API is not supported yet, you can write your own DNS API. If your API is not supported yet, you can write your own DNS API.

Loading…
Cancel
Save