January 10, 2023, 9:12am
Hi! the situation is:
main domain: example.com IP 22.214.171.124
sudomain: sub.example.com A record IP 126.96.36.199 (it's on a different hosting)
everything works fine, but unfortunately not with SSL
is it possible to do something in this situation? except to have everything with one ip and one hosting
P.S Plesk panel.
January 10, 2023, 9:15am
@lmz, and welcome to the LE community forum
Each system can obtain a cert for any FQDN that resolves via global DNS to an IP it controls.
IP 188.8.131.52 can get a cert for that domain.
IP 184.108.40.206 can get a cert for that domain.
January 10, 2023, 9:22am
Your subdomain on its different hosting should be able to get a certificate there: at its different hosting.
January 10, 2023, 9:44am
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 “220.127.116.11” that does not exist on this server.
but when i ping
sub.example.com i see IP 18.104.22.168 Why Cpanel sees wrong ip?
22.214.171.124 that IP for example.com, but not for sub.example.com
January 10, 2023, 9:51am
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.
January 10, 2023, 10:02am
Beats me, but that's hardly the scope of this Community IMO.
January 10, 2023, 10:18am
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
cinaitalia.org (plesk panel)
subdomain: tasks.cinaitalia.org (cpanel)
two different IP, main domain on plesk has additional A record: 126.96.36.199, subdomain it has everything by default, I don't understand why on the side cpanel, autossl fail
January 10, 2023, 10:42am
Maybe the multiple IPs has something to do with it:
Should that be one IP?, or two IPs??
January 10, 2023, 11:40am
188.8.131.52 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
184.108.40.206 and a 50 % chance of connecting to the incorrect IP address of
220.127.116.11. Doesn't sound correct to me.
Seems to be corrected currently, only a single IP address (
18.104.22.168) visible for the
tasks subdomain at the moment.
January 10, 2023, 1:04pm
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
February 9, 2023, 1:05pm
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.