Let's say, I own
example.com. It already points to a live website, which I do not under any circumstances want to accidentally prevent access to because of bumbling around with DNS settings.
I now have a new app engine project, my-project, that I want
myproject.example.com to point to.
How do I do this?
The documentation that I've found on this matter is confusing and ambiguous when it comes to subdomains. Other questions / answers concerning the topic, both here and stackoverflow, are out of date and contain 404 links.
The first problem I ran into, that whilst I had verified
example.com, I could not verify myproject.example.com - webmaster tools simply didn't want to validate it. And thus, this subdomain does not appear in the list of verified domains. So, as per the following image, I simply selected
example.com and asked to point a subdomain to my-project:
As you can see, Google asks you to add a bunch of DNS records. But where? Do I add them to
example.com or do I add them to
Since my DNS provider for
example.com cannot handle adding multiple IP addresses for a single A or AAAA record, I decided I wanted to use Cloud DNS instead. So I added a new zone for myproject.example.com, and added the A and AAAA records there:
But, it was not possible to add the CNAME record for
ghs.googlehosted.com. I don't know why, as there was no error message. The blue create button whizzes around a bit, then stops. No result.
And then we have the registrar setup, presumably where I have registered
example.com, on the same Cloud DNS zone setup page:
Which (sub)domain should these NS records go under? Are they NS records for
myproject.example.com (my best guess) or should they be additional NS records for
I'm clearly doing something wrong as visiting
myproject.example.com gives me a chrome ERR_NAME_NOT_RESOLVED.