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
Related
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 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.
The registrar for my domain is godaddy, I go to their DNS records section and I changed the A name to the elastic IP associated with my instance. Now when I type my domain in the browser, my website appears! However, it forwards it to the IP of my server.
Things I've tried (whether logical or not):
I'm using wordpress multsite so I changed the DOMAIN_CURRENT_SITE in wp-config.php to my new domain. No luck. Reverted.
I changed the 'site_url' and 'home' in my database to point to my domain. No luck. Tried one at a time etc. Reverted.
Changed ServerName to my new domain in httpd.conf (apache).
sudo hostname www.... (don't know what that does)
So I'd like to simply have my website open without it showing the IP in the address bar. Can someone help?
Thanks
EDIT:
Here's the DNS page of godaddy, I've blanked out the ip in the A records, but it's just the ip of my server.
First you need to set Custom NS in godaddy with AWS dedicated IPs then set them as DNS. If you are using Linux instance with cPanel then just add the domain in cpanel's addon-domain.
If you are using Windows instance then you should configure IIS.
I am close to tearing my hair out on this issue as I just cannot seem to get my Wordpress site to not read the Amaazon Public IP address.
I have a domain name in GoDaddy and have changed a host record so that my domain name "http://example.com" redirects to "http://0.0.0.0".
However once this page loads, the url quickly changes back to the Public IP address.
I have tried changing the Site URL in the Wordpress Settings but this just breaks the site and does not allow me to log in.
What is it I am doing wrong? I just cant figure it out. I just want the domain name from goDaddy to appear as the URL.
Thanks.
First of all attach the Elastic IP to your EC2 Instance so it wont change public IP after you shutdown and restart your machine. Make A Record in your Godaddy DNS Record File that points to the elastic IP.
You have not changed the base URL of your wordpress thats why it is still redirecting to the old Base URL. Connect to your EC2 instance and edit wp-config.php add the following line of code
define('WP_HOME','http://example.com');
define('WP_SITEURL','http://example.com');
I have my website http://www.mouryadandu.com which is hosted on photo shelter. I recently build a blog and wanted to host it on a separate hosting service. I already was having a multi site hosting service plan and decided to use add on domain to connect my blog. I have pointed the blog.mouryadandu.com subdomain to the server. The DNS propagation took few days but I was finally able to access the blog and successfully modify. Now when I share it, some people across the world are complaning they are seeing error 404 Page not Found. I also when share it on Facebook, its throwing error 404 instead of pulling the image. But for majority it seems not a problem , but I don't want this issue once the blog becomes permanent. I have a feeling there is something wrong with DNS settings, but when I ask my host, they say things are fine at their end. Does anyone have solution for this ?
It looks like your blog host has both IPv4 and IPv6 addresses:
blog.mouryadandu.com. 3600 IN CNAME cpanel17.fozzy.com.
cpanel17.fozzy.com. 14400 IN A 78.140.140.207
cpanel17.fozzy.com. 14400 IN AAAA 2a00:1178:1:43:4::11
When accessing via the 78.140.140.207 address (IPv4), I see your blog just fine. When accessing it via the 2a00:1178:1:43:4::11 address (IPv6), I get the cPanel redirect page (I assume this is the 404 people have been running into).
This is almost certainly a configuration error on the blog host. Can you try enabling IPv6 via cPanel (https://documentation.cpanel.net/display/ALD/Enable+IPv6)?