# DNS Manual Failure Going on 4.75 hours so far

**URL:** <https://community.letsencrypt.org/t/dns-manual-failure-going-on-4-75-hours-so-far/241622>\
**Category:** Help\
**Created:** [September 24, 2025, 8:49am UTC](https://community.letsencrypt.org/t/dns-manual-failure-going-on-4-75-hours-so-far/241622 "2025-09-24T08:49:06Z")\
**Posts on this page:** 3\
**Page:** 4

<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:** [October 1, 2025, 7:03pm UTC](https://community.letsencrypt.org/t/dns-manual-failure-going-on-4-75-hours-so-far/241622/62 "2025-10-01T19:03:25Z")

</div>

> [@dLubxiWGGVB8vXyLzUM3](#):
>
> If you have internal data

If you want some numbers, some data they released years ago are that [about 80% of validation attempts fail](https://community.letsencrypt.org/t/possible-new-feature-paused-acme-accounts/148364/7), and [closer to 85% over IPv6](https://community.letsencrypt.org/t/include-certificates-issued-via-ipv6-on-stats-page/189824/13). Since that time they've made some efforts at blocking "zombie clients" earlier in the process that just keep on retrying forever even though they haven't worked for years. In general I think the problem is with systems that retry too often (since they don't have an administrator paying any attention) rather than systems that don't retry often enough.

> [@dLubxiWGGVB8vXyLzUM3](#):
>
> My Acme client has to ask for new tokens again, your servers have to issue new tokens again, my servers need to publish the new tokens again, your servers need to attempt to verify the tokens again. It doesn't matter if I automate that on my end; it is still more steps and more computational work for both parties.

Well, the bandwidth and computational costs from trying again are much more than the costs of just making and tracking a new token, so I think it makes a lot more sense for the server to only retry (and with a new token) if requested to, and not just in the hopes that it might work eventually.

And as we keep saying, having an actual automated system, that can more smartly tell when to retry, and when to alert an administrator that multiple attempts don't seem to be working, really makes more sense from a wholistic perspective.

---

<div class="post-metadata">

**Author:** ![griffin](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/griffin/32/50204_2.png) [@griffin](https://community.letsencrypt.org/u/griffin)\
**Post date:** [October 2, 2025, 3:35am UTC](https://community.letsencrypt.org/t/dns-manual-failure-going-on-4-75-hours-so-far/241622/63 "2025-10-02T03:35:08Z")

</div>

Being an author, scientist, engineer, and software developer (and a rules lawyer in many games including MTG) rather seems to lead to a similar path of thinking of a lawyer in my experience. 🙂 I did consider the profession once, but assisting others (and myself) in the legal arena in minor matters taught me that I'm not particularly fond of courtrooms though I could probably bear it should the need arise. Having true discourse with individuals such as yourself makes me for the better, so for that I thank you. I've found that channeling passion/belief while maintaining one's temperament is a developed skill that can never be overvalued.

---

<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 1, 2025, 3:35am UTC](https://community.letsencrypt.org/t/dns-manual-failure-going-on-4-75-hours-so-far/241622/64 "2025-11-01T03:35:33Z")

</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/dns-manual-failure-going-on-4-75-hours-so-far/241622.md?page=3)
