mirror of
https://github.com/plantroon/acme.sh.git
synced 2024-12-24 22:21:40 +00:00
Updates to README.md
This commit is contained in:
parent
600a235140
commit
0aed065a75
@ -270,6 +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
|
||||||
|
|
||||||
**More APIs coming soon...**
|
**More APIs coming soon...**
|
||||||
|
|
||||||
|
@ -278,6 +278,32 @@ 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
|
||||||
|
|
||||||
|
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
|
||||||
|
into the FreeDNS website to read the HTML and posting updates as HTTP. The plugin needs to know your
|
||||||
|
userid and password for the FreeDNS website.
|
||||||
|
|
||||||
|
```sh
|
||||||
|
export FREEDNS_User="..."
|
||||||
|
export FREEDNS_Password="..."
|
||||||
|
```
|
||||||
|
|
||||||
|
You need only provide this the first time you run the acme.sh client with FreeDNS validation and then again
|
||||||
|
whenever you change your password at the FreeDNS site. The acme.sh FreeDNS plugin does not store your userid
|
||||||
|
or password but rather saves an authentication token returned by FreeDNS in `~/.acme.sh/account.conf` and
|
||||||
|
reuses that when needed.
|
||||||
|
|
||||||
|
Now you can issue a certificate.
|
||||||
|
|
||||||
|
```sh
|
||||||
|
acme.sh --issue --dns dns_freedns --dnssleep 30 -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…
Reference in New Issue
Block a user