We build websites on SiteGround and have bumped into an issue with a client that has DNS and domain hosted at another (non-SiteGround) provider, with various services attached, such as FTP and email.
Typically we build the site, let's say for "example.com" and if DNS is external, we launch by asking the DNS manager to add an a record to the SiteGround IP. Historically, clients have done this by adding the 'a record' to the root, and then resolving 'www.' to the root, so that www and non-www are resolved to the SiteGround website.
It is in this context that we have always issued SSL certificates successfully from the SiteGround side, since SiteGround checks to see if traffic (non-www and www) is routed to their IP before issuing the cert.
NOW HERE IS MY ISSUE:
A recent client has said that they will only add the 'a record' for 'www.' and not for the non-www within DNS. They say this might break or cause issues with other services like FTP, etc.
I said "Okay" because sure, I will do whatever the clients wants, but SiteGround states that I cannot successfully issue an SSL from within their hosting panel when only the www is pointed to SiteGround and the non-www is NOT. They say this is not possible.
So my final question is: who is correct? SiteGround? Or the client's DNS manager who says I should be able to issue this cert just fine based on only his www 'a record'?