Networking error looking up TXT

Issuance Tech
1

Getting a few of these since 7:30pm central:

During secondary validation: DNS problem: networking error looking up TXT for [domain]

We run pre-flight checks before we attempt issuance and our DNS probes are succeeding ok, so I'm wondering maybe some kind of technical issue happening?

2

Yea I'm seeing the same.

Invalid status. Verification error details: During secondary validation: DNS problem: networking error looking up

3

I am having this issue as well.

4

We're having the same issue as well.

5

They've got pretty good monitoring; I'm sure they'll have someone looking at it shortly.

6

I'm another one experiencing this. Is it a temporary outage? Or a configuration issue?

Having IPv6 disabled shouldn't be a problem, right?

7

me too

8

Same incident, same window, from a different angle: http-01 (not dns-01), zones
kroboth-home.at and cactis.eu on Cloudflare (dave/melany.ns.cloudflare.com).
All times UTC, 2026-09-11:

  • 00:41–00:48 — six production finalizations failed with
    urn:ietf:params:acme:error:caa: "Error finalizing order :: rechecking caa: During
    secondary validation: While processing CAA for mx1.kroboth-home.at: DNS problem:
    networking error looking up CAA"
  • 00:53 — a production order for mail.cactis.eu succeeded, between the failures
  • 01:08–01:14 — five production authorizations for mail.kroboth-home.at failed with
    urn:ietf:params:acme:error:dns: "During secondary validation: DNS problem: networking
    error looking up A ... AAAA" (hit the 5/hostname/hour cap)
  • 01:19–01:32+ — identical failures on staging (separate account)

While the failures were still occurring (01:24–01:33) the zones looked clean from
everything we can reach: unboundtest.com NOERROR 9/9 for A/AAAA/CAA on all three names
with no timeouts, letsdebug.net clean, and every authoritative response is ≤381 bytes
(algorithm 13, no truncation at bufsize 512, TCP fine, both NSes identical).

A success sandwiched between failures for the same account and zones 5 minutes apart
looks like a subset of secondary-validation perspectives failing, not a full outage.

Failed authorization URLs if a look at the server side helps:

production (account 3720971846):
https://acme-v02.api.letsencrypt.org/acme/authz/3720971846/777491053696   01:08:46
https://acme-v02.api.letsencrypt.org/acme/authz/3720971846/777495044656   01:14:28
staging (account 335460303):
https://acme-staging-v02.api.letsencrypt.org/acme/authz/335460303/4563139333   01:19:15
https://acme-staging-v02.api.letsencrypt.org/acme/authz/335460303/4563386783   01:26:16
9

My guess is a temporary outage.

If your domain is configured to be only accessible by IPv4, that's fine. If only accessible by IPv6, that's also fine. If accessible by both, definitely fine. The only problem is when your domain says it's accessible by one of those means (though an A or AAAA record) but in fact it isn't through that one.

10

They've posted a status update; I recommend checking there for updates: