Networking error looking up A/AAAA/TXT

Help
1

My domain is: portal.invsoftcol.com (also happening on panel.invsoftcol.com and portal.invsoftcol.com)

I ran this command:

certbot certonly --webroot -w /var/www/certbot -d panel.invsoftcol.com
certbot certonly --webroot -w /var/www/certbot -d portal.invsoftcol.com

It produced this output:

Certbot failed to authenticate some domains (authenticator: webroot). The Certificate Authority reported these problems:
  Domain: portal.invsoftcol.com
  Type:   dns
  Detail: During secondary validation: DNS problem: networking error looking up A for portal.invsoftcol.com; DNS problem: networking error looking up AAAA for portal.invsoftcol.com

My web server is (include version): nginx/1.24.0 (Ubuntu) — system nginx as reverse proxy in front of Docker containers

The operating system my web server runs on is (include version): Ubuntu 24.04

My hosting provider is: Contabo

I can login to a root shell on my machine (yes or no, or I don't know): Yes

I'm using a control panel to manage my site (no, or provide the name and version of the control panel): No — hand-managed nginx config + Docker Compose

The version of my client is: certbot 2.9.0, installed via snap (certbot 5.8.0 snap revision 5893, classic confinement)

DNS is hosted on GoDaddy (ns05.domaincontrol.com / ns06.domaincontrol.com), same zone invsoftcol.com.

  • 3 other subdomains on this exact same zone (apidian, api.pos, api.admin, staff) issued successfully in the past 48h with the same setup.

  • portal.invsoftcol.com is a brand-new subdomain, never used before, no prior DNS history — created purely to rule out any caching/history effect on panel.invsoftcol.com, which has the identical error.

  • The exact same "networking error during secondary validation" also happens with dns-01 (manual TXT via GoDaddy API) and with --staging, so it's not challenge-type-specific or rate-limit related.

  • dig +short A portal.invsoftcol.com resolves cleanly and instantly from 8.8.8.8, 1.1.1.1, and both authoritative nameservers directly.

  • https://letsdebug.net reports "All OK" for panel.invsoftcol.com (http-01).

This looks like it might be related to Let's Encrypt's remote/secondary validation perspectives being unable to reach GoDaddy's authoritative nameservers for this zone specifically — any pointers on which remote perspective is failing, or whether this is a known GoDaddy interaction issue, would help a lot.

2

There was a recent incident that is now resolved. Does this error persist for you?