Need help activating Let's Encrypt for A record with different IP

Hi! the situation is:
main domain: example.com IP 11.11.11.11
sudomain: sub.example.com A record IP 22.22.22.22 (it's on a different hosting)

everything works fine, but unfortunately not with SSL :slight_smile: is it possible to do something in this situation? except to have everything with one ip and one hosting

P.S Plesk panel.

Hi @lmz, and welcome to the LE community forum :slight_smile:

Each system can obtain a cert for any FQDN that resolves via global DNS to an IP it controls.

IP 11.11.11.11 can get a cert for that domain.

IP 22.22.22.22 can get a cert for that domain.

3 Likes

Your subdomain on its different hosting should be able to get a certificate there: at its different hosting.

3 Likes

But what if the autossl is not issuing a certificate? there Cpanel

An error occurred the last time AutoSSL ran, on January 10, 2023:
A DNS (Domain Name System) or web server misconfiguration may exist. The domain “sub.example.com” resolved to an IP address “11.11.11.11” that does not exist on this server.

but when i ping sub.example.com i see IP 22.22.22.22 :slight_smile: Why Cpanel sees wrong ip?
11.11.11.11 that IP for example.com, but not for sub.example.com

That sounds like two different DNS systems are in use.
DNS should be global and synchronized.
If you care to share some real details, maybe we can unravel this issue.

4 Likes

Beats me, but that's hardly the scope of this Community IMO.

4 Likes

of course two different, because there two different hosting, the main domain has an A record with the ip of another hosting and that's it

main domain: cinaitalia.org (plesk panel)
subdomain: tasks.cinaitalia.org (cpanel)

two different IP, main domain on plesk has additional A record: 88.99.27.19, subdomain it has everything by default, I don't understand why on the side cpanel, autossl fail

Maybe the multiple IPs has something to do with it:

Name:      tasks.cinaitalia.org
Addresses: 46.4.90.206
           88.99.27.19

Should that be one IP?, or two IPs??

4 Likes

46.4.90.206 seems to be the apex domains IP address.. So any client connecting to the tasks subdomain had a 50 % chance of connecting to the correct IP address of 88.99.27.19 and a 50 % chance of connecting to the incorrect IP address of 46.4.90.206. Doesn't sound correct to me.

Edit:
Seems to be corrected currently, only a single IP address (88.99.27.19) visible for the tasks subdomain at the moment.

4 Likes

Yes, you are right, I did not notice this, this "record A" plesk panel automatically substitutes this entry, thanks for the help, I figured out the error, the topic is closed

2 Likes

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