I am setting up a website for a client which I will be hosting and maintaining, and I am trying to determine what will be the most pain free setup. My thought is to do the following:
1) Set up the clients domain at client.mydomain.com 2) Have the client update their dns records for *.client.com to CNAME client.mydomain.com
From a practical perspective, this feels best for me because then I don't have to maintain access to their DNS control panel especially if they want to do other things with it. Furthermore, if I decide I need to move the website to a different host, I can do it seamlessly without their even knowing just by updating where client.mydomain.com points.
This being said, my concern is that I will affect the SEO for client.com. If I impact SEO at all, I will just go with the A-Record route and call it good...but if there is no impact, this seems nicer to me.
Thoughts?
(As an aside, I do have google maps included in this app, and the API key is yelling at me when I hit the app from a different tld...client.mydomain.com and client.com. Is there a way to ask for a single google api key that can work with cname'd domains? I can work this out in code, but didn't know if there was a simpler solution.)