I am trying to point a domain from a website (radicalxchange.org) currently hosted by Firebase to a new version hosted in a Digital Ocean droplet. The name servers are managed by AWS Route53. When I change the A record in Route53 to my D.O. droplet IP address (167.99.59.52), the site immediately stops loading. I've tried to wait a few hours but it never connects.
I should note that Route53 contains a lot of other stuff related to our site (CNAME, MX & TXT records) however I've been under the impression that the only thing necessary to route website traffic to the new IP is the A record. What am I doing wrong?
Well, your Digital Ocean droplet is kind of misconfigured:
1) from current hosting, you have permanent redirect to https (and if your browser have that already cached, it will immediately go to https://radicalxchange.org), and you don't have https configured in your new hosting
2) Even if you use clean browser, your new http://radicalxchange.org will redirect you to http://167.99.59.52/, which is quite strange.
I suggest you hardcode 167.99.59.52 radicalxchange.org entry in your hosts file, and test thoroughly, and only then make DNS changes.
Related
I have the domain 'alexdollard.xyz' registered with Google domains
I added the custom resource record 'wp' as a type A, and pointed it to my digitalOcean droplet (a Wordpress instance)
I then added a CNAME record for www, and pointed it at my Netlify-hosted site. (This Netlify site is a gatsby/react site which will query my wordpress instance for blog-post data)
When I ping the IPv4 address of the wp subdomain in my terminal, I get a response. But when I ping 'wp.alexdollard.xyz', I get unknown host. And when I run it in the browser I get "wp.alexdollard.xyz’s server IP address could not be found."
I've been working with this subdomain for a while now and this issue just started. wp.alexdollard.xyz was working until yesterday.
I have already tried renewing my DHCP Lease, flushing my dns cache, and changing my DNS servers to public servers. For context, this issue didn't start until I deployed the site to Netlify, and pointed the google DNS name servers for alexdollard.xyz to the Netlify name servers. But wp.alexdollard.xyz should still point to this digitalOcean droplet since it's a subdomain, right?
I'm sorry if this question is sophomoric or dumb, it's possible that I really just don't understand the basics of DNS configuration. Seems like something simple is going on. What is causing this issue with my DNS?
DNS entry seem correct:
dig a wp.alexdollard.xyz
;; ANSWER SECTION:
wp.alexdollard.xyz. 3600 IN A 134.209.73.194
it is also resolving globally: https://www.whatsmydns.net/#A/wp.alexdollard.xyz
I can see two options here:
your local DNS is stil propagating or needs to be flushed
your droplet is not accepting this domain
Can someone answer a simple SSL Cert question for me to derisk my decision?
My Stack: Bitami WordPress instance on GCP VM.
Situation
I have a website with an SSL cert linked to my domain name.
I started an instance with a new static IP address.
I remapped the domain name to the new servers and added the correct credentials [confirmed everything is configured correctly with the GCP team].
Ran -dig command and confirmed new instance is mapped to the domain name.
Problem
The domain name will not load in the browser. Get the "NET:: ERR_CERT_INVALID" message.
My Diagnosis
I haven't transferred my SSL to my new IP address.
Confusion
Everywhere I read says the SSL is mapped to the domain name, not the IP address itself. So theoretically there should not be an issue.
Question(s) to you
Do I solve this simply by generating new SSL cert on the new instance? Will that just overwrite the old SSL cert and map my domain name to the new SSL cert?
If not - what's the solution?
I don't understand the technical relationship between IP address, domain names, and certs. I have read as much as I can and everyone seems to talk around it but not explain it in detail.
Thanks in advance!
Bitnami Engineer here,
If you created a new instance from scratch, you will need to migrate the SSL certificates from the first instance to the second one. You can either copy the SSL certificates from the machine or download them again from the CA website and substitute the files you have in the /opt/bitnami/apache2/conf folder.
In case you were using a Let's Encrypt certificate, you can generate new certificates by using the Bitnami HTTPS configuration tool (/opt/bitnami/bncert-tool) or by running the CLI tool to generate new certificates. If you use the Bitnami HTTPS configuration tool, you won't need to modify the Apache's configuration, the tool will do that for you. You can learn more about it here
https://docs.bitnami.com/google/how-to/understand-bncert/
Please remember to confirm that the domain name is configured properly by checking your domain using this online tool before trying to generate the certificates
https://www.whatsmydns.net/
New problem.
I used the bncert tool as per Jotas recommendation and it worked well.
I checked my domain name via 'whatsmydns' as well as my SSL via an SSL checking tool. All worked out as expected - my IP address is matching against my Domain name and SSL is matching against my domain name.
I type my domain name into the browser and it loads my site with the padlock, across all browsers.
So from the outside - it looks like everything is fine.
But I have two issues still.
Problem #1:
In my WordPress 'general>settings', I tried to update my 'WordPress address' and 'site address' but they are greyed out. So I updated my wp-config file with the new https addresses as per these instructions which have worked for me before without issues (https://www.wpbeginner.com/wp-tutorials/how-to-change-your-wordpress-site-urls-step-by-step/). It didn't break the site, but I could no longer log in. As soon as I deleted the new wp-config code, I could log in again. So if that won't work, I now have no course of action to update my 'WordPress' and 'site' addresses.
So my questions are - do you know why this won't work? Is it a bitnami quirk? And does it matter? If the domain is working, does it matter if I keep the wp-config file as an http address and not an https address?
Problem #2:
My domain name takes me to my site at the correct IP address. It loads with a secure padlock icon. I can log in. Everything works as it should.
If I use the IP address, however, instead of the domain name, it also loads the same site but as an insecure site with no padlock.
Question - Any idea how that is possible? I thought a domain name was just a human-friendly version of an IP address. And if the webserver is a single server, how can using a domain name versus an IP address generate different front end results?
Thanks again team, as a person who is new to this community, it really does give you faith in humanity.
I have a webiste hosted in a web hosting which is down.
My domain was pointing to this website hosting so I changed DNS records to a new hosting because we didn't recieve any emails.
In this new hosting, I changed MX records to GSuite and email is working OK.
I need to get a backup from my webiste so when the web hosting which is down comes up, I want to point my DNS for http to that webhosting so I can access the site. After backup is done, I will revert my DNS changes back so all is resolved in my new hosting.
Is there any way I can do this at DNS level without affecting the current MX records which are working OK?
Regards
I solved by changing "A" DNS record to point to the older server DNS IP.
I have my Google Domains DNS configures to point to my Digital Ocean droplet, but my site will not load. I should at least get a notice that my NGINX proxy server is receiving the request, but I'm not. I usually use NameCheap, but I thought Google might be better, and I'm having trouble getting it to work.
However, When I visit my site, the page says that the site can't be reached. [Site is unavailable][3]
Any insights?
Thanks in advance.
Your domain name tannerplauche.com works fine for me. Apparently, it's just propagation time on your end. When you change the DNS, the changes do not take effect instantly. Normally, your local ISP's server updates data every 24-48 hours. Once the cache on the local ISP's server is cleared, you will see the website on your end as well.
In the meantime, you may bypass propagation by checking your domain name via proxy server. Here ist he link: https://kproxy.com/
Right now I have a domain ex: foobar.com hosted on Bluehost.
I created an instance on AWS and fortunately, I used (wordpress by bitnami) to migrate my foobar.com to the aws site.
I created an elastic ip and associated it with my instance.
This is where I am stuck. I've read tons of tutorials telling me to go into my Bluehost and add a DNS record which I haved.
My first attempt was to do a URL redirect on foobar.com, which worked but only for the homepage because when I would navigate to another page, it would display the elastic ip (ex: 53.13.153.12/about).
I am unsure how to go about this problem.
Setup an A Record, not a URL redirect. You'll need to then configure the vhost on your server to understand that domain (I think you may have already done this step).
Bluehost has some documentation here