# DNS problem: SERVFAIL looking up CAA (solved)

**URL:** <https://community.letsencrypt.org/t/dns-problem-servfail-looking-up-caa-solved/109397>\
**Category:** Help\
**Created:** [December 27, 2019, 9:38am UTC](https://community.letsencrypt.org/t/dns-problem-servfail-looking-up-caa-solved/109397 "2019-12-27T09:38:19Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![munmar](https://avatars.discourse-cdn.com/v4/letter/m/7ab992/32.png) [@munmar](https://community.letsencrypt.org/u/munmar)\
**Post date:** [December 27, 2019, 11:13am UTC](https://community.letsencrypt.org/t/dns-problem-servfail-looking-up-caa-solved/109397/3 "2019-12-27T11:13:58Z")

</div>

Thanks for your feedback @mnordhoff

Does it make sense that an authorization request for “[graphql.test.nexoya.io](http://graphql.test.nexoya.io)” results in an error for “[test.nexoya.io](http://test.nexoya.io)”?

By the way, your dig request for `graphql.test.nexoya.io` yields results back.

---

_[View the full topic](https://community.letsencrypt.org/t/dns-problem-servfail-looking-up-caa-solved/109397)._