github-repos/acme.sh
1
0
Fork 0
mirror of https://github.com/acmesh-official/acme.sh.git synced 2025-02-06 04:34:41 +08:00
Code Issues Packages Projects Releases Wiki Activity

Updated DNS alias mode (markdown)

neil 2018-02-12 21:48:03 +08:00
parent 1041391be6
commit 196d78c4a2
1 changed files with 32 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

32
DNS-alias-mode.md

@ -117,5 +117,37 @@ Let's assume the first domain `aliasDomainForValidationOnly.com` is hosted at cl
Do not remove the CNAME like : `_acme-challenge.importantDomain.com` after you issue the cert. It will be reused when acme.sh tries o renew the cert. The left cname record `_acme-challenge.importantDomain.com` doesn't harm to your domain at all. Just keep it there. Do not remove the CNAME like : `_acme-challenge.importantDomain.com` after you issue the cert. It will be reused when acme.sh tries o renew the cert. The left cname record `_acme-challenge.importantDomain.com` doesn't harm to your domain at all. Just keep it there.
### 6. challenge-alias or domain-alias
We have another parameter: `--domain-alias`, it has the same meaning with `--challenge-alias`.
But with `--domain-alias` you don't need to add `_acme-challenge.` prefix.
For example, if you use `--challenge-alias`, you must set CNAME like bellow:
```sh
CNAME:
_acme-challenge.A.com
=> _acme-challenge.B.com
```
Then issue cert like:
```sh
acme.sh --issue -d a.com --challenge-alias b.com --dns dns_cf
```
If you use `--domain-alias`, the CNAME should be like:
```sh
CNAME:
_acme-challenge.A.com
=> myalias.B.com
```
Then issue cert like:
```sh
acme.sh --issue -d a.com --domain-alias myalias.B.com --dns dns_cf
```