I had an operational and accessible Bitnami Wordpress site on Lightsail with my domain at GoDaddy. My cert expired so I went to renew it, and also switch my domain from living at GoDaddy to being at Google Domains. Ever since, I haven't been able to load the site by IP or domain. Are there any good guides specifically for configuring this set up?
Bitnami Engineer here,
Please ensure your domain points to the correct IP address (the one assigned to your instance). You can verify that using this online tool:
https://www.whatsmydns.net/
If the domain doesn't resolve to the correct IP address, you will need to update the DNS records in your DNS provider dashboard. Once you confirm everything is configured correctly, you should be able to renew your certificate.
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 migrated my website to the Google Cloud servers. I have pointed the old DNS to the Google DNS and I have setup the DNS zone with an A record for the main domain pointing to the IP of the Google Cloud server and a CNAME record for the www subdomain. However, when I type the domain name in the browser, it loads the Google Cloud IP, but the browser doesn't show the domain name but the IP address.
You need only one DNS entry for the instance;
www aliased (A) to the (external) IP address of the server.
From your description I guess that you configured your Cloud DNS in a correct way and that your domain registrar is pointing to GCP DNS servers:
nameServers:
- ns-cloud-a1.googledomains.com.
- ns-cloud-a2.googledomains.com.
- ns-cloud-a3.googledomains.com.
- ns-cloud-a4.googledomains.com.
Nevertheless make sure your DNS configuration looks similar to this:
If you need to add some records to your DNS here's some usefull documentation on how to add records to do it. You can use both console or gcloud utility for this.
You may also have a look at the documentation on how to migrate to GCP from other providers.
But - I suspect some tricky-webserver configuration issue here. Why ?
You pointed out that you can reach your website - but instead of domain name you see a real IP of your site in the browser. That may be the result of a specific configuration that "redirects" you to a certain IP after detecting you used domain name to get to the server.
Please inspect your webserver's configuration and try to point out a real cause of this.
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.
I have been looking around the internet and I have come across a few different ways to link my AWS EC2 instance to my domain name. It looks like I could do it using Route 53 but I am not entirely sure on that process. The other way is to map it from google. These seem like the best instructions I have found for that: link a Google Domain to Amazon ec2 server
The question that I can not seem to find is what about my email address. I pay google so that I can have some email addresses name#mydomain.com. Now these work fine and I have had them up and running for months. But now I want to have my website (it is a web app) point to it. Because currently when you go to mydomain.com it says This site can’t be reached mydomain.com’s server IP address could not be found.
Some help here on how to do this would be great. I am afraid that I am going to set this up incorrectly and then lose access to my gmail account which I cannot have happen.
Your domain's email is configured via MX DNS records. You would point your domain to your EC2 instance by adding A or CNAME DNS records. The two configurations are completely separate. You will not break your current email setup by adding an A or CNAME record that points to the EC2 instance. You simply need to add that record in your DNS settings, wherever your DNS is currently hosted. You don't need to make any changes in your Gmail account configuration, and you don't really need to use Route53 either (although it does add some nice features). You had to configure the MX records somewhere at some point, to setup your G-Suite account for your domain. You just need to go into that same DNS configuration (most likely still hosted at the company where you initially purchased the domain name) and add an additional record.
I am new in the Amazon EC2 world, I just created an app, that is located URL like this:
http://ec2-54-123-45-678.compute-1.amazonaws.com:8080
This is generated URL by Amazon EC2.
Now I would need to use my own domain name, so when I would access www.my-domain-name.com, I would like to see the content from
http://ec2-54-123-45-678.compute-1.amazonaws.com:8080
I bought the domain name on Godaddy.
Is there any way to do this in Amazon AWS dashboard or do I need to set it up in Godaddy system?
Thanks
I am answering on a more general level because I stumbled upon this thread when setting my custom domain.
In Amazon I created an instance and associated an IP to that instance. You were able to access it by typing in the amazon url
I actually used Media Temple not GoDaddy, but it will be similar. I went to the zone file and added that public url to the www
And as you can see, here is my blog actually working on the custom domain.
I set the wildcard because that way, no matter what someone types, if it is not set, then they will still see the site.
EDIT
For the root URL you should be entering your elastic IP and setting that as an A record.
First you need to set an ElasticIP for associated to that instance.
Then point the DNS entry of "www" for "my-domain-name.com" to the IP assigned in the step above.
Where you manage your DNS is another thing, can be in GoDaddy or in AWS Route53. You must adjust the delegation DNS in the "my-domain-name.com" register. Ex: your domain can be registered with GoDaddy but its delegation DNS point to Route53 so you can manage the domain from your AWS Console.
In order to setup DNS mapping you can map the existing IP 54.123.45.678 to ex: www.my-domain-name.com.
However, as you are running tomcat which is running at 8080 you need to forward the the request to the tomcat using Apache. So that you can visit www.my-domain-name.com without port 8080. If you are using linux box install Apache, apache-modjk and then configure sites.