bryan/www
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Merge upstream

Browse Source
This commit is contained in:
Bryan Roessler
2022-10-10 12:47:38 -04:00
parent f4ebff5cda
commit fd4e05cc7d
80 changed files with 1685 additions and 3017 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
blog.bryanroessler.com/_posts/2019-02-09-automatic-certbot-namecheap-acme-dns.md
View File

@@ -164,9 +164,9 @@ The step I'm sure you've been waiting for.
A wild goose chase:
1. LetsEncrypt first asks your <yoursite\>.com domain for the TXT record at _acme-challenge.example.com to complete the challenge
2. The Namecheap DNS server responds with a CNAME record that points to ch30791e-33f4-1af1-7db3-1ae95ecdde28.acme.<yoursite>.com, so LetsEncrypt goes there instead
3. The authoritative DNS server for \*.acme.<yoursite\>.com is ns1.acme.<yoursite\>.com, which points at your server IP (running acme-dns)
4. LetsEncrypt can finally ask ns1.acme.example.com what is the TXT record for ch30791e-33f4-1af1-7db3-1ae95ecdde28.acme.<yoursite\>.com and acme-dns will answer that question
2. The Namecheap DNS server responds with a CNAME record that points to ch30791e-33f4-1af1-7db3-1ae95ecdde28.acme.*yoursite*.com, so LetsEncrypt goes there instead
3. The authoritative DNS server for \*.acme.*yoursite*.com is ns1.acme.*yoursite*.com, which points at your server IP (running acme-dns)
4. LetsEncrypt can finally ask ns1.acme.example.com what is the TXT record for ch30791e-33f4-1af1-7db3-1ae95ecdde28.acme.*yoursite*.com and acme-dns will answer that question
### Additional Considerations