I have created django website on Google cloud and its running on sql instance (https://school-website-272007.el.r.appspot.com).
I already have a google domain, and i want to link this to it.
I followed as below:
Created a VM instance on GCP and linked the external ip to my running sql instance.
Created Zone and 'A' / 'CNAME' in the Cloud DNS section.
Added the new DNS settings to Google domain - DNS settings under custom.
(used https://cloud.google.com/dns/docs/quickstart and other youtube links to perform)
But still my google domain is not able to link to the website (https://school-website-272007.el.r.appspot.com)
Can anyone help?
I recommend to use App Engine Custom Domains. With custom domains you can add the domain you may want to redirect to your App Engine app instead of using the appspot link.
While configuring the custom domain, it will tell you which DNS records you have to add to your DNS.
Related
My client has a domain configured in a different provider and I built a website in AWS. We want to use their sub domain created in the different provider but the think is: they are using this domain to a different site as well, so they cannot set it via DNS server name; the second possibility would be via IP, however my IPs are not defined as I'm using Amplify to build the site.
Is there any other way we can connect their sub domain to my website?
Our two first options were: DNS server name but they are using te main domain to another site, so it would cause another issue and IP address but my IP are not defined as I'm using amplify to build.
I expect to be able to connect my website to their sub domain that is located in a different provider.
In the Amplify console, go to Domain management under your app settings. From there, add your domain and make sure to exclude the root since you only want to set up a subdomain. You can view the required DNS records from there. Basically you will need to set up a CNAME on your DNS configuration.
This documentation might help - https://docs.aws.amazon.com/amplify/latest/userguide/to-add-a-custom-domain-managed-by-a-third-party-dns-provider.html
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 an issue, or perhaps an understanding problem with linking my domain with AWS. I will use the xy.ro domain as an example.
I have the xy.ro domain registered with easyhost.com. On AWS I have a node.js express web app.
My xy.ro domain is not working as it does not point to anything.
I tried to create a hosted zone on AWS with the xy.ro domain and tried to create a dataset for this domain but it does not work.
I tried to find step by step instructions also on AWS and other providers but I did not find anything.
Can someone point me into the right direction?
If your domain xy.ro is registered with easyhost.com then it would presumably also be using their DNS hosting service to serve your DNS records.
Creating a public hosted zone in AWS won't affect the DNS resolution unless you can migrate your name servers to use Route 53.
I was not able to see steps from easyhost.com website, however from the AWS side take a look at this documentation.
You should be able to copy the name servers and update within easyhost so that it will use Route 53 as your DNS provider instead.
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.
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).