# LE DNS still doesn't find TXT record when all others tested do

**URL:** <https://community.letsencrypt.org/t/le-dns-still-doesnt-find-txt-record-when-all-others-tested-do/226918>\
**Category:** Help\
**Created:** [October 4, 2024, 11:06am UTC](https://community.letsencrypt.org/t/le-dns-still-doesnt-find-txt-record-when-all-others-tested-do/226918 "2024-10-04T11:06:38Z")\
**Posts on this page:** 6\
**Page:** 2

<div class="post-metadata">

**Author:** ![lifeboy](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/lifeboy/32/7458_2.png) [@lifeboy](https://community.letsencrypt.org/u/lifeboy)\
**Post date:** [October 5, 2024, 9:38am UTC](https://community.letsencrypt.org/t/le-dns-still-doesnt-find-txt-record-when-all-others-tested-do/226918/21 "2024-10-05T09:38:27Z")

</div>

I have found the xfr:ipaddress directive which can be added to MIAB's DNS secondaries config and that notifies the secondary of DNS updates immediate, which seems to have solved the problem.

I'm doing more testing, and will report if anything is not yet working correctly in this regard.

---

<div class="post-metadata">

**Author:** ![lifeboy](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/lifeboy/32/7458_2.png) [@lifeboy](https://community.letsencrypt.org/u/lifeboy)\
**Post date:** [October 7, 2024, 12:38pm UTC](https://community.letsencrypt.org/t/le-dns-still-doesnt-find-txt-record-when-all-others-tested-do/226918/22 "2024-10-07T12:38:02Z")

</div>

It turns out that the xfr: protocol doesn't automatically trigger a secondary to update from the primary. Does anybody have advice on how this can be done, specially in the context of MIAB and PowerDNS?

---

<div class="post-metadata">

**Author:** ![linkp](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/linkp/32/60089_2.png) [@linkp](https://community.letsencrypt.org/u/linkp)\
**Post date:** [October 7, 2024, 12:48pm UTC](https://community.letsencrypt.org/t/le-dns-still-doesnt-find-txt-record-when-all-others-tested-do/226918/23 "2024-10-07T12:48:27Z")

</div>

In BIND we simply configure where to send notifications when the zone changes. You may get better answers to that question by asking in either MIAB or PowerDNS forums. It's pretty off-topic here.

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [October 7, 2024, 12:51pm UTC](https://community.letsencrypt.org/t/le-dns-still-doesnt-find-txt-record-when-all-others-tested-do/226918/25 "2024-10-07T12:51:05Z")

</div>

One simple hack may be to lower the "`refresh`" and "`retry`" for the domain.

```nohighlight
fast.za.net
        primary name server = ns1.box2.gtahardware.co.za
        responsible mail addr = hostmaster.box2.gtahardware.co.za
        serial = 2024100515
        refresh = 7200 (2 hours) <<<<<<<<<<<<<<<<<<<<<
        retry = 3600 (1 hour) <<<<<<<<<<<<<<<<<<<<<
        expire = 1209600 (14 days)
        default TTL = 86400 (1 day)

```

---

<div class="post-metadata">

**Author:** ![lifeboy](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/lifeboy/32/7458_2.png) [@lifeboy](https://community.letsencrypt.org/u/lifeboy)\
**Post date:** [October 7, 2024, 4:32pm UTC](https://community.letsencrypt.org/t/le-dns-still-doesnt-find-txt-record-when-all-others-tested-do/226918/26 "2024-10-07T16:32:07Z")

</div>

I have taken this up with PowerDNS, which is not accepting the DNS change notify... thanks all for your assistance which is much appreciated!

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [November 6, 2024, 4:33pm UTC](https://community.letsencrypt.org/t/le-dns-still-doesnt-find-txt-record-when-all-others-tested-do/226918/27 "2024-11-06T16:33:03Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

[Previous page](https://community.letsencrypt.org/t/le-dns-still-doesnt-find-txt-record-when-all-others-tested-do/226918.md?page=1)