I'm working on this problem since hours. I read that I should include an A DNS record for a www. part of my domain. I tried it all, even a wildcard. Could you help me? My DNS records are set correctly or did I miss anything? I include a screenshot of my AWS config: [image] My domain is: ripped.l…

I had to update my personal data associated with this domain. The error I get now is a different. Bad gateway?! Not sure why that one happens. Any ideas? 2021/08/03 11:56:05.503 INFO tls.issuance.acme.acme_client trying to solve challenge {"identifier": "ripped.link", "challenge_type": "…

AWS Route 53 Domain Registration sometimes acts as a reseller for Gandi. Was the domain bought through AWS directly?

In any case: there's nothing "misleading" about the error: that's just what the Let's Encrypt validation servers DNS resolver sees.. And also the rest of the world.

Yeah! I never heard of Gandi. :slight_smile:

Thanks for your response mate! I have other domains too and will check if those maybe work, of if this is a general problem. I am the registered owner (I guess, since I ordered over AWS).

Yeah the domain is registered by me. Weird enough that let's encrypt worked for me with other domains (but not with caddy, just with the certbot standalone).

[image] raphaellueckl: Wait, I see name servers being listed, or am I missing something? That's just the WHOIS information. Apparently this info is not known at the .link nameservers.

Were the other domains you've used (that work) also .link or were they other TLDs? You can look at AWS's documentation on supported TLDs and see that .link is done through Gandi. But in any event, AWS isn't currently giving you the product you've bought, as you've registered the name but the .link …

[image] petercooperjr: contact AWS Support Thanks I will get in contact with them. :slight_smile:

The "BAD GATEWAY" seems to be generated when the ACME client tries to obtain a cert from ZeroSSL. 2021/08/03 11:56:10.871 ERROR tls.obtain could not get certificate from issuer {"identifier": "ripped.link", "issuer": "acme.zerossl.com-v2-DV90", "error": "provisioning client: HTTP 504: <htm…

Misleading Error? "DNS problem NXDOMAIN looking up A"

Help

raphaellueckl July 17, 2021, 7:08am 10

Wait, I see name servers being listed, or am I missing something?

Topic		Replies	Views
New to Let’s Encrypt and Caddy, Must be missing a step Help	15	5807	July 6, 2024
Some challenges have failed - Godaddy domain forwarded ( redirected ) to aws Help	19	2072	August 15, 2020
Sudden issues with Caddy to get HTTPS for my local IP (DNS and ACME related i guess) Help	22	6074	June 1, 2024
I'm having trouble generating the let's encrypt certificate Help	36	605	May 20, 2026
Can't obtain a cert even after paying for domain Help	93	2161	January 5, 2023

Misleading Error? "DNS problem NXDOMAIN looking up A"

Related topics