My domain is: producks.xyz
My web server is (include version): Amazon Linux 2
The operating system my web server runs on is (include version): Centos(7)
My hosting provider, if applicable, is: Namecheap
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 1.3.0
I have filled out the above but I am not actually stuck with creating my certificate - I have managed to do all that correctly. I generated my certificate using certbot and I am using nginx.
The issue I am facing is that in order to verify my domain, I needed to add an A record in my DNS in order to prove I owned it. This A record pointed
@ and the
www sub domain to my EC2 Public IP, which all worked fine in terms of validation.
The problem is, my front end server (which is hosted on Vercel/Zeit Now) is now saying there is a DNS conflict - which makes sense, because there is now an A record pointing the domain root (
www to my backend server IP.
My thought to fix this is carry out the steps I did with certbot previously, but to a subdomain, like
api.domain.com. However is there a way I can have this set up so that the backends URL is
domain.com and not a subdomain?