大网数据广告活动
网站运营与故障问答

Wildcard certificate with certbot and DNS challenge

· 52CE 我爱测

I am trying to obtain a wildcard certificate from Let's Encrypt for my web server. Since I am using a "local" hoster, certbot has no DNS authenticator plugin for it. So I have to use the manual method. Doing this, certbot wants m…

问题原文

原帖链接 · stulleman · CC BY-SA 4.0

I am trying to obtain a wildcard certificate from Let's Encrypt for my web server.

Since I am using a "local" hoster, certbot has no DNS authenticator plugin for it. So I have to use the manual method.

Doing this, certbot wants me to add two DNS TXT records. For this I log in to my managment console from my "local" hoster and add the TXT records.

When applying the changes, it says that it can take up to 48 hours for the changes to be known world wide.

My question now is, how can this work when it takes so long for the changes to propagate?

Second question: Am I doing this right? Can I have two DNS TXT entries with the same host? Or should I edit the first one when I am asked to add the second one? Then it would take even longer.

已采纳解答

原帖链接 · Anthony Geoghegan · CC BY-SA 4.0

how can this work when it takes so long for the changes to propagate?

The propagation time (“up to 48 hours for the changes to be known world wide”) is a conservative estimate of the time that various DNS servers around the world may have records for your domain stored in their internal cache. However, when carrying out its DNS validation (as per the ACME protocol), Let’s Encrypt does not use recursive name servers. When it checks the TXT resource records for your domain, it queries the authoritative name server(s) directly – so there’s no delay.

Am I doing this right? Can I have two DNS TXT entries with the same host? Or should I edit the first one when I am asked to add the second one? Then it would take even longer.

Yes, you are doing this right. As per the DNS standards, it’s fine to have multiple TXT records for the same (sub)domain. Here’s an example of how the dig utility might return results for the _acme-challenge.example.com domain in order to validate an X.509 certificate for both example.com and *.example.com:

$ dig _acme-challenge.example.com TXT
...
;; ANSWER SECTION:
_acme-challenge.example.com. 3600 IN     TXT     "TXrF987Uc1aEl4TTm7LL76rrN3wba9q6kkTmcNJnjNk"
_acme-challenge.example.com. 3600 IN     TXT     "L3f2m9APvpIlamHHtZ2deRvDdhSPMcMmvPHsvSsln9o"
...

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Webmasters Stack Exchange
适用范围
以原帖系统、软件版本与发布日期为准(2018-09-04)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 4.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。