LE doesn't resolve my hostname

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:
217-19-15-110.coreixcloud.net

I ran this command:
virtualmin certbot (unsure of the command)
also happens on Proxmox

It produced this output:
Domain: 217-19-15-110.coreixcloud.net
Type: dns
Detail: DNS problem: NXDOMAIN looking up A for
217-19-15-110.coreixcloud.net

My web server is (include version):
Apache 2.4

The operating system my web server runs on is (include version):
CentOS 6

My hosting provider, if applicable, is:

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):
Virtualmin

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

Hi @lucian,

Welcome to the community forum!

Using unboundtest.com to perform a test, I’ve verified that your domain is failing to return an A record.

2 Likes

It looks to me like your authoritative nameservers don’t support 0x20 case randomization. Here’s an example querying authns1.coreix.net. directly:

$ dig +short @193.26.222.1 217-19-15-110.coreixcloud.net
217.19.15.110
$ dig @193.26.222.1 217-19-15-110.cOreIXCLOUd.NET | grep "status"
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 2816
4 Likes

Thanks, that’s actually helpful. Let’s see how we can solve this.
Wish the unboundtest.com pointed this out, too.

1 Like

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