Not able to get SSL - DNS SERVFAIL

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. crt.sh | 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: email.copozo.com

I ran this command: certbot --apache

It produced this output:17: email.copozo.com

My web server is (include version):Server version: Apache/2.4.6 (CentOS)

The operating system my web server runs on is (include version):centos 7

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

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):Certbot failed to authenticate some domains (authenticator: apache). The Certificate Authority reported these problems:
Domain: email.copozo.com
Type: dns
Detail: DNS problem: SERVFAIL looking up A for email.copozo.com - the domain's nameservers may be malfunctioning; DNS problem: SERVFAIL looking up AAAA for email.copozo.com - the domain's nameservers may be malfunctioning

A post was split to a new topic: How ,can I get a SSL certificate

@abhinav: I don't see any current problems, and it looks like you've created at least 4 certificates today. Are you still having trouble? (If so, creating more certificates isn't likely to help you, and you'll run into rate limits to prevent abuse of Let's Encrypt's resources.)

@Sadiq1: Could you create your own new thread in the Help section please? Your question is broad, and if you could answer the questions about your domain name, how you administrate the site (through a control panel, are you administrating Apache or nginx or something else, etc.), and so forth, it will help people help you.

4 Likes

@petercooperjr yes there was no issue with certbot part. Issue was at our hosting provider. Sincere apologies for trying to create certificate couple of time, while debugging the issue it happened that we requested for certificate 4 time.
Issue is now resolved.
Thanks for your reply.

3 Likes

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