Subdomain - DNS problem: NXDOMAIN looking up A

My domain is:

I ran this command:
/opt/letsencrypt/letsencrypt-auto certonly --debug --webroot -w /var/www/ -d -d --config /etc/letsencrypt/config.ini --agree-tos

It produced this output:

My web server is (include version):

The operating system my web server runs on is (include version):
Linux/unix EC2 instance

uname -r


My hosting provider, if applicable, is:

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

I’m using a control panel to manage my site (no, or provide the name and version of the control panel):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot):
/opt/letsencrypt/letsencrypt-auto --version
certbot 1.7.0

Hi all, I have a peculiar situation, and maybe it can’t even be done. I’m loosely following this guide (

But here’s the problem:
I have a digital ocean bucket I’m using for my client
I have an AWS EC2 instance for my backend
I have only one domain name (

I’m using the networking tab in Digital Ocean to point a subdomain to my EC2 instance, so I can create a cert for it and not have to buy another domain name.

I’m not even sure if this is possible, but since it’s a backend API, I don’t really care what the name is, therefore I don’t want to spend more money on it, but I want the benefits of TLS.

I’m getting the error above, even thought I have an A record pointing to that IP address. Any ideas?

tl;dr; I want SSL/TLS on my backend service, but I don’t want to pay for another domain name, so I created a subdomain and am pointing to AWS from Digital Ocean. Not sure if this is even possible.

1 Like

Hi @sergnio

now there is no ip address defined -

Host Type IP-Address is auth. ∑ Queries ∑ Timeout A yes 11 0
AAAA yes A yes 11 0
AAAA yes

Not non-www, not www. Your check - there you had an A record with your non-www, but not with your www, so the NXDomain-result is expected.

If you want to create a certificate via http validation, an A record is required.


@JuergenAuer , thank you for the quick reply.
So again, I’m changing these DNS records on digital ocean to point to an AWS EC2 instance.
Not sure if this is even allowed.

But I added an A record for and an A record for per your suggestion.

Now I’m getting this error, even though both addresses have an IP associated with them

Type:   unauthorized
Detail: Invalid response from
[]: 404
To fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address.
- The following errors were reported by the server:

Type:   dns
Detail: No valid IP addresses found for

When I go to, in my web browser I go directly to my instance, which is contradicting the Detailed error message

1 Like

Looks like some of your name servers are very slow.

Try it one time again. Your last check - - looks ok.

1 Like

@JuergenAuer really, thank you so much for all your help. It turns out all I had to do was wait.
This tool is fantastic! Does your tool force the DNS servers to look for new DNS assignments? Or how does that work?


The tool checks always first the root servers to find the authoritative name servers of the domain.

Then these name servers are checked, so the results are not cached.

It’s an own dns client.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.