Reverse DNS & Letsencrypt
I'v several VPS with different providers.
When I have set reverse dns as f.e. linode.mydomain.ext and it resolves I add letsencrypt like:
sudo certbot --apache -d linode.mydomain.ext
linode.mydomain.ext is an A record from my DNS setup elswhere. So linode A ip
That works well on all my VPS's, but with Linode the certificate is made with a 'link' to li1422-xx.members.linode.com (old Reverse DNS) so the page generates an SSL error. The SSL certificate is generated and exepted by Letsencrypt, but the webpage will generate an SSL error so wont be load in your browser.
How can I avoid this? I don't understand.
3 Replies
If you've already followed this process (e.g., if that's what "When I have set reverse dns as f.e. linode.mydomain.ext" meant), then you may just need to wait a bit longer for the DNS changes to propagate fully, in particular to whatever servers the LetsEncrypt infrastructure is using for its reverse lookups, as the original records may still be cached.
-- David
@GASOLINE:
Hi,
That works well on all my VPS's, but with Linode the certificate is made with a 'link' to li1422-xx.members.linode.com (old Reverse DNS) so the page generates an SSL error. The SSL certificate is generated and exepted by Letsencrypt, but the webpage will generate an SSL error so wont be load in your browser.
How can I avoid this? I don't understand.
I don't understand. Could you explain what you mean by a "link"? What does Certbot output? What's your real hostname? What error messages do you receive? What's going wrong?
What's your OS, Certbot version, Apache configuration…?
@db3l:
If you've already followed this process (e.g., if that's what "When I have set reverse dns as f.e. linode.mydomain.ext" meant), then you may just need to wait a bit longer for the DNS changes to propagate fully, in particular to whatever servers the LetsEncrypt infrastructure is using for its reverse lookups, as the original records may still be cached.
Let's Encrypt doesn't do reverse DNS lookups.
Also, Let's Encrypt doesn't issue certificates for *.members.linode.com hostnames.
dig -x your.linode's.ip.address
You can follow this guide to set your Linode's PTR record: