# \#dns

**URL:** https://community.letsencrypt.org/tag/dns/3.md

[Latest](https://community.letsencrypt.org/latest.md) · [Categories](https://community.letsencrypt.org/categories.md) · [Tags](https://community.letsencrypt.org/tags.md)

---

## [DNS Resolver Upgrade To Unbound 1.19](https://community.letsencrypt.org/t/dns-resolver-upgrade-to-unbound-1-19/210418)

<div class="topic-metadata">

**Author:** [@jcjones](https://community.letsencrypt.org/u/jcjones)\
**Replies:** 1\
**Last updated:** [December 20, 2023, 8:14pm UTC](https://community.letsencrypt.org/t/dns-resolver-upgrade-to-unbound-1-19/210418 "2023-12-20T20:14:31Z")

</div>

Let’s Encrypt recently updated to Unbound 1.18, which enforces more strict compliance with RFC 2308. We announced this change belatedly here. Today we updated our Staging environment to Unbound 1.19. This upgrade has a…

---

## [DNS Resolver Upgraded to Unbound 1.18, Empty Responses require SOA sections](https://community.letsencrypt.org/t/dns-resolver-upgraded-to-unbound-1-18-empty-responses-require-soa-sections/210417)

<div class="topic-metadata">

**Author:** [@jcjones](https://community.letsencrypt.org/u/jcjones)\
**Replies:** 0\
**Last updated:** [December 19, 2023, 7:41pm UTC](https://community.letsencrypt.org/t/dns-resolver-upgraded-to-unbound-1-18-empty-responses-require-soa-sections/210417 "2023-12-19T19:41:28Z")

</div>

On November 28th, Let’s Encrypt updated our Production environment to Unbound 1.18, which enforces more strict compliance with RFC 2308, section 3: Name servers authoritative for a zone MUST include the SOA record of t…