I've recently converted from using traditional registrars and started using Google for website hosting and domain registration. I've followed various guides and am currently infuriated at how hard it is to connect my domain owned by google to the google cloud instance while retaining email forwarding.
In order to point the domain to my VM in requires changing the nameservers. Once the name servers are changed then email forwarding stops working. I'm stuck in an infuriating loop. There has to be a better way.
Here's the process I followed
Google Domain > ExampleSite.com
Google Domain > support#examplesite.com (email forwarding to default gmail account)
Google Cloud > Create Wordpress VM instance
Google Cloud > Add DNS Records
Google Domains > Update Nameservers with info from Google Cloud DNS
Works, but email forwarding is immediately disabled unless I revert to default google nameservers, which stops the domain from pointing to the VM.
Please. Anyone. Help with a better way of doing this. Please. I'm so frustrated.
Thank you.
The reason why email forwarding breaks that your Cloud DNS is not configured with the necessary MX records. Here are the two possible solutions:
Add the MX records described here to your Cloud DNS configuration.
Revert back to Google Domain's name servers, which has the MX records built in. You can then set up your website by creating an A Record for the # record and www subdomain record to point to your GCE's IP address.
If all you want to do is to host a website I recommend (2), as it saves you the cost and complexity of having Cloud DNS as well as Google Domains.
Related
Hej!
I own a domain registered through GCP and it's connected with Cloud DNS in GCP, I would be very happy if you could help me setup my custom domain for my web page at buahaha.github.io.
I think I know how to do this, because I did it before with other domain(s), but this time something is not working as it should. I have set up even a TXT record, and it does not propagate through DNS servers, and the same goes for my CNAME record. I attach screenshots of my setup below.
It's strange to me as it is the basic setup for this kind of service, and I'm really confused...
Pozdrawiam,
Szymon 🎶
In addition to #blacha answer, here are some links and guidance. Once you use Cloud Domain to register a domain, there is an option where you can use which DNS provider that you use for your domain. These are Cloud DNS, Google Domains and Custom Name servers.
If by chance you get confused which DNS server that you are using I suggest to DIG your domain to see which name server that you are using just to make sure you are using the correct DNS server.
Since this concern choses Cloud DNS here is the link that you can follow on how to create zone, configure A record connecting to the domains IP address and creating Cname record for the subdomain that you desire.
The problem was that I had to explicitly choose Cloud DNS as my DNS provider. If you have set your DNS zone already, just choose it from the drop-down menu, otherwise create your own...
I have mistakenly registered a domain in the wrong project from Google Cloud > Network Services > Cloud Domains.
Is there a way for me to move it in another project?
Google Domains is not project based. Domains are managed by the identity of the domain owner.
Google Cloud Domains is in preview and is project based. At this time, there is no method to move a registered domain from one project to another. You can export the domain to Google Domains. Note: The DNS servers for a domain can be located in any project and do not need to be in the same project as Google Cloud Domains. Before exporting the domain, check to see if your domain is already being managed by Google Domains here. You will need to be using the same identity that owns the registered domain. If the domain appears, go to the other project, create the DNS servers and then enter the servers into Google Domains on the DNS tab under Name Servers. You can also change the DNS servers while in Google Cloud Domains. Select "EDIT DNS DETAILS" at the top of the Google Cloud Domains console window.
If you mean that you created the DNS server in one project and you need to move the DNS server to another project then follow these steps. Create a new DNS server in the desired project, duplicate the DNS server resource records and then update the DNS server entries in Google Domains. Wait at least 24 hours and then delete the old DNS server.
If you mean that your registered your domain under the wrong Google Account (email identity), then you can transfer the domain to the desired Google Account. Login to Google Domains with the account that you own the domain. In the interface follow the Transfer a domain out section. Get the authorization code. In another browser window, login with the desired account and transfer in the domain using the transfer authorization code.
I have bought a domain name on Google Domains, installed Wordpress Multisite on a Google Cloud VM with Compute Engine, setup a load balancer with 2 instances and an Active Google Managed certificate.
I have followed the instructions at https://cloud.google.com/load-balancing/docs/https/ext-https-lb-simple and pointed the Google DNS at the Load Balancer. I currenty get:
The website working in http (not secure) with the direct IP of the VM.
The balancer switching between the two IPs if I enter the https address (ie returning Page served from: lb-backend-pubdeals-x06k) but not returning the wordpress site.
Address is https://pub.deals
But what I want is someone to type in http://pub.deals and https://pub.deals and get the secure site.
Does anyone have instructions on how to redirect users who arrive at http://pub.deals are then redirected to https://pub.deals?
Thanks Jay
So John Hanley was right, I was over complicating things. For the last 20 years or so I've used hosting companies for my sites, and taken care of ssl when I needed to within wp-config and .htaccess, but this is my first time using google cloud and vm builds, so I followed their docs to apply a google managed ssl. They say in order to issue a google managed sll you need to have a load balancer set up, so I rtfm and set one up. It worked as far as the user was delivered to a secure site of either one of two instances, but I couldn't figure out how to attach them to my vm instance with wordpress on it and hence get my content displayed. I did get the http --> https forward using these docs (https://cloud.google.com/load-balancing/docs/https/setting-up-http-https-redirect) but I still didn't manage to connect the whole affair to the VM with wordpress on it.
TLDR; I deleted the load balancers and google certificate and did it through wordpress.
I am using Google domains and had an email forwarding set up to my Gmail account.
Recently I have set up Google Cloud DNS to be able to use Google Cloud CDN and speed up my site.
Unfortunately, when setting up Google Cloud DNS I had to change the default Google domain name servers. This has disabled email forwarding from Google domains.
Does anyone know how to set up email forwarding to Gmail directly from the Google Cloud Platform?
I managed to find a solution in the cloud-dns-discuss Google group.
Google Domains documentation to set up email forwarding with custom name servers recommends using Blank or # as Name/Host/Alias.
I was using #. After removing the # and leaving the Name/Host/Alias Blank, e-mail forwarding started working.
We wanted a subdomain http://magento.ngstorefront.com to point to a VM on Google Cloud. We could not find clear docs on this.
What we did:
Deployed a Magento Google Click to Deploy VM from marketplace
Assigned a Static ip address to the VM --> 35.193.85.53
The default Magento site loads at http://35.193.85.53
To have the sub-domain http://magento.ngstorefront.com load the site (loading at http://35.193.85.53). So we added a new A record for "magento.ngstorefront.com --> 35.193.85.53" in Google Cloud DNS
On the domain registrar (Google Domains), we added a Registered host (magento.ngstorefront.com) and a Custom Record as below.
But the site doesn't load at http://magento.ngstorefront.com What are we missing?
The subdomain is resolving now. Wanted to add the answer.
The mistake we did was to create the subdomain A record in Registrar (Google Domains). Although registered in GoogleDomains, our primary domain ngstorefront.com is pointing to Siteground
So we have to add the A record in Siteground instead of GoogleDomains , like this
Updated on 3/15/2019
While the above solved the issue of IP address pointing and loading Magento, but we had one issue where the URL would change to IP instead of staying as http://magento.ngstorefront.com
To solve the above, do this:
Login to Magento Admin > Stores > Configuration > General > Web > Base URLs
And enter the domain name you want Magento to use.
Based upon the answer provided, I'd say that the problem is, still having set siteground.us as NS.
You'd have to change the NS records to Cloud DNS name-servers at Google Domains, then it would resolve through Cloud DNS and the zone-file can be maintained there (as you've tried without effect).