DNS problem: SERVFAIL, while trying to renew my certificate

[Nella]

My domain is: nellserv.duckdns.org

I ran this command: sudo certbot --apache

It produced this output:

Saving debug log to /var/log/letsencrypt/letsencrypt.log

Which names would you like to activate HTTPS for?
We recommend selecting either all domains, or all domains in a VirtualHost/server block.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
1: nellserv.duckdns.org
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Select the appropriate numbers separated by commas and/or spaces, or leave input
blank to select all options shown (Enter 'c' to cancel): 
Renewing an existing certificate for nellserv.duckdns.org

Certbot failed to authenticate some domains (authenticator: apache). The Certificate Authority reported these problems:
  Domain: nellserv.duckdns.org
  Type:   dns
  Detail: DNS problem: SERVFAIL looking up A for nellserv.duckdns.org - the domain's nameservers may be malfunctioning; no valid AAAA records found for nellserv.duckdns.org

Hint: The Certificate Authority failed to verify the temporary Apache configuration changes made by Certbot. Ensure that the listed domains point to this Apache server and that it is accessible from the internet.

Some challenges have failed.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.

My web server is (include version): Apache/2.4.52 (Ubuntu)

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

My hosting provider, if applicable, is: Orange

I can login to a root shell on my machine: yes

I'm using a control panel to manage my site: no

The version of my client is: certbot 2.11.0

I have done it in the past, ports 80 and 443 are open, i have no idea what's wrong at this point. I would be very grateful for your help <3.

[MikeMcQ]

Welcome to the community @Nella

I think the duckdns DNS servers may be down or having problems. I cannot query them either. Check their system status or just wait a while and see if it clears

I only tried 2 of the 9 auth servers but neither responded. Some of the other tools we use to check DNS could not reach them either.

dig A nellserv.duckdns.org @ns1.duckdns.org
;; communications error to 99.79.143.35#53: timed out
;; communications error to 99.79.143.35#53: timed out
;; communications error to 99.79.143.35#53: timed out

dig A nellserv.duckdns.org @ns2.duckdns.org
;; communications error to 35.182.183.211#53: timed out
;; communications error to 35.182.183.211#53: timed out
;; communications error to 35.182.183.211#53: timed out

Oddly, using https://unboundtest.com saw the correct A record (but did not run it numerous times).

dnsviz tests reported similar problems as above