# Why has DNS-01 to be such complicated?

**URL:** <https://community.letsencrypt.org/t/why-has-dns-01-to-be-such-complicated/98827>\
**Category:** Issuance Tech\
**Created:** [July 30, 2019, 9:29pm UTC](https://community.letsencrypt.org/t/why-has-dns-01-to-be-such-complicated/98827 "2019-07-30T21:29:50Z")\
**Posts on this page:** 5\
**Page:** 2

<div class="post-metadata">

**Author:** ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)\
**Post date:** [August 11, 2019, 10:44pm UTC](https://community.letsencrypt.org/t/why-has-dns-01-to-be-such-complicated/98827/21 "2019-08-11T22:44:43Z")

</div>

With DANE, your browser trusts the certificates that your signed TLSA record specifies. Meaning all your trust is in ICANN to not misuse the root KSK. At least today with CAs, we have 4 major root programs and one of them (Mozilla) is completely managed in the open. But seeing as how no browsers implement DANE and DNSSEC deployment is pitiful, it is a moot point for now.

FWIW the ACME WG really did not like the “static CNAME” idea (like what ACM implements) when it was posted to the mailing list. Most members seem to believe that it is an “end run” of validation practices. But I’m still unconvinced that a single CNAME indirection on its own is enabling Amazon to do what they do.

---

<div class="post-metadata">

**Author:** ![Bachsau](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/bachsau/32/81693_2.png) [@Bachsau](https://community.letsencrypt.org/u/Bachsau)\
**Post date:** [August 11, 2019, 10:50pm UTC](https://community.letsencrypt.org/t/why-has-dns-01-to-be-such-complicated/98827/22 "2019-08-11T22:50:00Z")

</div>

> [@\_az](#):
>
> Meaning all your trust is in ICANN

But that is already the case as long as we use public DNS at all, so it is not more of a problem than it has been forever, and ICANN can do nothing without the world getting aware of it.

---

<div class="post-metadata">

**Author:** ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)\
**Post date:** [August 11, 2019, 10:57pm UTC](https://community.letsencrypt.org/t/why-has-dns-01-to-be-such-complicated/98827/23 "2019-08-11T22:57:24Z")

</div>

Yeah, you’re totally right, my feelings about DNS overall bleeding through 😊.

---

<div class="post-metadata">

**Author:** ![Bachsau](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/bachsau/32/81693_2.png) [@Bachsau](https://community.letsencrypt.org/u/Bachsau)\
**Post date:** [August 11, 2019, 11:00pm UTC](https://community.letsencrypt.org/t/why-has-dns-01-to-be-such-complicated/98827/24 "2019-08-11T23:00:58Z")

</div>

At least there is nothing completely secure, something can only be _more_ secure. Someone could drop some nuclear bombs and we’ll be all dead. 😉

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [September 10, 2019, 11:01pm UTC](https://community.letsencrypt.org/t/why-has-dns-01-to-be-such-complicated/98827/25 "2019-09-10T23:01:02Z")

</div>

Closed on September 10, 2019, 11:01pm UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

[Previous page](https://community.letsencrypt.org/t/why-has-dns-01-to-be-such-complicated/98827.md?page=1)
