[SOLVED] The server could not resolve a domain name


#1

I’m trying run auth for my server the first time. I’ve tried manual, and standalone auth (running nginx on jessie). I’ve verified that the ports are open. I’ve had my domain for nearly a decade, but I can’t get an auth to succeed. Despite all my different auth methods I continually get the following message and my whitelisted domain is an A record.:

2015-10-29 13:18:54,181:INFO:letsencrypt.reporter:Reporting to user: The following ‘unknownHost’ errors were reported by the server:

Domains: example.org
Error: The server could not resolve a domain name

Does anyone have an ideas/suggestions?

Thanks!


#2

How does your command look like? example.org is a special domain that can’t be registered, so what’s your actual domain? Can you share it?


#3

This is the command that I’m using. When prompted, I cut and paste the blurb, and verify the link is working.

sudo ./letsencrypt-auto --agree-dev-preview --server https://acme-v01.api.letsencrypt.org/directory -d example.org --authenticator manual auth

After a few moments, the result is:

Failed authorization procedure.example.org (simpleHttp): unknownHost :: The server could not resolve a domain name :: No IPv4 addresses found for example.org

IMPORTANT NOTES:
 - The following 'unknownHost' errors were reported by the server:

   Domains: example.org
   Error: The server could not resolve a domain name

   To fix these errors, please make sure that your domain name was
   entered correctly and the DNS A/AAAA record(s) for that domain
   contains the right IP address.

#4

Resolves fine here, so probably an issue with LE’s DNS configuration. We already have such issues when we used Google’s DNS servers instead of the system one for a library.


#5

Well thanks for double checking. I was afraid it might be an upstream error, but was hoping I was just doing something boneheaded.


#6

After a little more testing, using the default server (e.g. not specifying --server https://acme-v01.api.letsencrypt.org/directory ) I was able to get the client to work properly and create certificates. Still no luck using the beta server though. :frowning:


#7

I tried again this morning, and still nothing. I then proceeded to delete my subdomain’s CNAME record from DNS. I was then able to successfully obtain a cert for that subdomain, and the domain. I’ve recreated the CNAME, and now everything is working fine.


Not actually whitelisted yet?
#8

Where did the CNAME record point to?


#9

Hello Evryone,
I am having troubles renewing our domain certificates that expired on May, 09 this year.
Question: Is there a way to generate the certificates ONLINE and download them to the file system?
Thanks for any help.
Regards.


#10

This seems to be in the wrong place…
You are adding a question to a closed ticket.
I don’t even know how it was able to get here!
3 years later
You should really open a new ticket for your requet.