# Shouldn't verification via DNS record be a priority?

**URL:** <https://community.letsencrypt.org/t/shouldnt-verification-via-dns-record-be-a-priority/604>\
**Category:** Issuance Tech\
**Created:** [August 31, 2015, 9:24am UTC](https://community.letsencrypt.org/t/shouldnt-verification-via-dns-record-be-a-priority/604 "2015-08-31T09:24:54Z")\
**Posts on this page:** 1\
**Showing post:** 48

<div class="post-metadata">

**Author:** ![jcjones](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/jcjones/32/78_2.png) [@jcjones](https://community.letsencrypt.org/u/jcjones)\
**Post date:** [January 21, 2016, 11:26pm UTC](https://community.letsencrypt.org/t/shouldnt-verification-via-dns-record-be-a-priority/604/48 "2016-01-21T23:26:28Z")

</div>

> [@gfunkdave](#):
>
> Cool! How does it work? I can't find documentation anywhere.

The protocol specification is in ACME: [draft-ietf-acme-acme-01](https://tools.ietf.org/html/draft-ietf-acme-acme-01#section-7.5)

There are a few [clients](https://community.letsencrypt.org/t/list-of-client-implementations/2103) that support it already. [letsencrypt.sh](https://github.com/lukas2511/letsencrypt.sh) is one I know of.

---

_[View the full topic](https://community.letsencrypt.org/t/shouldnt-verification-via-dns-record-be-a-priority/604)._