+ CNAME in format of DNS zone file; duplicate spaces removed.

Alexey Vazhnov 2020-04-11 20:24:07 +03:00
parent 6915d1293f
commit a3700a91b3

@ -1,18 +1,24 @@
If your dns provider doesn't support api access, or if you're concerned about security problems from giving the dns api access to your main domain, then you can use DNS alias mode.
If your DNS provider doesn't support API access, or if you're concerned about security problems from giving the DNS API access to your main domain, then you can use DNS alias mode.
For example, your main domain is `example.com`, which doesn't have api access, or you don't want to give the api access to acme.sh, since it's important.
For example, your main domain is **example.com**, which doesn't have API access, or you don't want to give the API access to acme.sh, since it's important.
And you have another domain: "aliasDomainForValidationOnly.com", which has a supported dns api. This domain is less important, and maybe it's used for validation only.
And you have another domain: **aliasDomainForValidationOnly.com**, which has a supported DNS API. This domain is less important, and maybe it's used for validation only.
Ok, let's start.
### 1. First set domain CNAME:
```sh
```text
_acme-challenge.example.com
=> _acme-challenge.aliasDomainForValidationOnly.com
```
or, in standard [DNS zone file](https://en.wikipedia.org/wiki/Zone_file) format, (like ISC BIND or NSD):
```text.zone_file
_acme-challenge.example.com IN CNAME _acme-challenge.aliasDomainForValidationOnly.com.
```
### 2. Issue a cert:
@ -151,7 +157,6 @@ Then issue cert like:
acme.sh --issue -d a.com --domain-alias myalias.B.com --dns dns_cf
```
**Note:** Don't use the domain name only for --domain-alias.
```sh
acme.sh --issue -d a.com --domain-alias B.com --dns dns_cf