证书颁发机构今天开始检查DNSSEC
Cert Authorities Check for DNSSEC from Today

原始链接: https://www.grepular.com/Cert_Authorities_Check_for_DNSSEC_From_Today

## 证书颁发机构现在必须进行DNSSEC验证 自2026年3月15日起,证书颁发机构(CA)**必须**验证已启用DNSSEC的域名对应的DNSSEC记录。这意味着CA必须在证书颁发过程中(例如ACME)验证DNS响应的真实性——包括确定证书颁发权限的CAA记录。 作者成功运行DNSSEC 14年,预计CA已经为这一变化做好了准备,但现在强制执行已正式生效。 虽然DNSSEC可能看起来很复杂,但文章鼓励域名所有者——特别是那些阅读技术博客的人——**检查他们的注册商是否支持DNSSEC**并考虑启用它。这可能是一个简单的步骤,可以显著提高域名安全性。

一项针对证书颁发机构 (CA) 的新要求将于 2026 年 3 月生效,该要求将在为启用 DNSSEC 的域名颁发证书时强制进行 DNSSEC 验证——Let's Encrypt 已经这样做。然而,DNSSEC 的采用率仍然极低,即使是在热门网站中也是如此。 对排名前 1000 位的域名(通过 Tranco List)的分析显示,DNSSEC 的普及率仅为个位数,排名前 100 位的域名中更是低至 2%。值得注意的是,一年多的监测显示,只有三个域名的 DNSSEC 状态发生了变化,其中 Canva 曾短暂禁用过它。 作者得出结论,DNSSEC 在很大程度上是“停滞的”,尽管它在保护域名免受某些攻击方面具有好处,但很少有网站所有者积极考虑或实施它。DNS 服务提供商鼓励启用 DNSSEC,因为它会因配置的复杂性和潜在的灾难性错误而增加客户锁定。
相关文章

原文
View Markdown Other Articles

Article written by a human: Mike Cardwell

About 14 years ago I set up DNSSEC. I've been running it on all of my domains ever since, without issue. First using bind9 and then later using PowerDNS.

From today, all Certificate Authorities (CAs) must validate DNSSEC when a domain has it enabled.

So from today, when a CA looks up my CAA record to see if they are allowed to issue a cert for one of my domains, they must validate that the response they received is valid. And during the ACME dance, they have to validate those DNS records too.

I assume that all CA's had implemented this requirement prior to today, if only so they could test it before the deadline was reached. But now it is mandatory, and I expect that any evidence that they are not doing it will be treated harshly.

You might not want to learn about DNSSEC. You probably don't host your own DNS zone. There's a reasonable chance you own your own domain name though if you're here reading this. Why not go find out if your registrar supports DNSSEC for your domains? It might be a one click operation to turn it on...

联系我们 contact @ memedata.com