# DNS-01 challenge fails since unbound 1.18. TXT records can be fetch using unbound 1.16 but not 1.18 1.19

**URL:** <https://community.letsencrypt.org/t/dns-01-challenge-fails-since-unbound-1-18-txt-records-can-be-fetch-using-unbound-1-16-but-not-1-18-1-19/210708>\
**Category:** Help\
**Created:** [December 26, 2023, 12:22pm UTC](https://community.letsencrypt.org/t/dns-01-challenge-fails-since-unbound-1-18-txt-records-can-be-fetch-using-unbound-1-16-but-not-1-18-1-19/210708 "2023-12-26T12:22:58Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![petercooperjr](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/petercooperjr/32/84698_2.png) [@petercooperjr](https://community.letsencrypt.org/u/petercooperjr)\
**Post date:** [January 3, 2024, 5:21pm UTC](https://community.letsencrypt.org/t/dns-01-challenge-fails-since-unbound-1-18-txt-records-can-be-fetch-using-unbound-1-16-but-not-1-18-1-19/210708/17 "2024-01-03T17:21:33Z")

</div>

[@lestaff](https://community.letsencrypt.org/groups/lestaff) Hoping that it's okay to start bugging you and you're back from the holidays. 🙂

Between this thread, and [another similar recent report](https://community.letsencrypt.org/t/dns-challenge-for-many-domains-failes-with-cnames/211072), it looks like there was some sort of regression in Unbound (either the updated version or in configuration) for the use case of multiple (20+) domains using DNS-01 where the challenge record for all of those domains is CNAME'd to one single record which is populated with all the TXT entries for all of them.

Not a _particularly_ common configuration, no, but it is [described as a standard way for acme.sh's alias mode](https://github.com/acmesh-official/acme.sh/wiki/DNS-alias-mode#3-share-the-same-aliased-domain) for a multiple-SAN certificate, so it might be something that others are trying too. (And I think it _should_ be working.)

---

_[View the full topic](https://community.letsencrypt.org/t/dns-01-challenge-fails-since-unbound-1-18-txt-records-can-be-fetch-using-unbound-1-16-but-not-1-18-1-19/210708)._
