I ran this command: certbot certonly --webroot --config le-config.ini --non-interactive -d rednour.net -d www.rednour.net
It produced this output: Challenge failed for all domains. Upon looking up the challenge, it showed that it was having trouble getting the A records for my domain name on both the WWW and non-WWW. This is strange because I checked and made sure that the records are available via dig, dnschecker.org, intoDns, and Google Dig. Any ideas if this is a problem with Let’s Encrypt or the DNS provider?
It’s worth noting that I have issued certs for other domins both before and after attempting this domain, which would lead me to believe the issue is somewhere outside of my usage of certbot.
That's curious, because Letsencrypt uses an unbound version with the same configuration.
And your dns131.a.register.com is buggy:
Nameserver doesn't pass all EDNS-Checks: dns131.a.register.com: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
May be the reason "dns timeout"
"DNS problem: query timed out looking up A for www.rednour.net
DNS problem: SERVFAIL looking up A for rednour.net
Runs there an old dns software?
PS: There is no older certificate, so it's your first certificate.
With what you have shared it leads me to think the problem lies with the DNS provider’s namerservers behaving incorrectly. I think the best bet would be to move nameservers and see if that works.