# DNS challenge is in staging

**URL:** <https://community.letsencrypt.org/t/dns-challenge-is-in-staging/8322>\
**Category:** Feature Requests\
**Created:** [January 5, 2016, 11:51pm UTC](https://community.letsencrypt.org/t/dns-challenge-is-in-staging/8322 "2016-01-05T23:51:10Z")\
**Posts on this page:** 1\
**Showing post:** 20

<div class="post-metadata">

**Author:** ![pfg](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/pfg/32/1924_2.png) [@pfg](https://community.letsencrypt.org/u/pfg)\
**Post date:** [January 11, 2016, 11:31am UTC](https://community.letsencrypt.org/t/dns-challenge-is-in-staging/8322/20 "2016-01-11T11:31:44Z")

</div>

Let’s Encrypt does authoritative lookups (i.e. starting from root servers). You can simulate that with `dig example.com +trace`. Maximum TTL is limited to [a few minutes](https://community.letsencrypt.org/t/le-using-chached-dns-lookups-during-dv-process/2591/6?u=pfg) on their end.

---

_[View the full topic](https://community.letsencrypt.org/t/dns-challenge-is-in-staging/8322)._
