I followed this tutorial in order to setup CloudFlare with Digitalocean.com. However, I encountered the following problem:
Visiting my website from Chrome, I noticed that there is nothing indication that CloudFlare is working for me. There are no CF-RAY or cloudflare nginx headers on responses. Also the Claire extension showed that the CloudFlare is not active. However, when I test the website with WebPagetest, I can see that all the javascript files where served with CloudFlare caching system.
How long did you wait to test? DNS changes take time to propagate, it sounds like your DNS server is still using the old server address.
Check by running ping address.com, does it resolve to your digital ocean IP or something else?
CloudFlare is usually set-up at a nameserver level (though CloudFlare Partners alongside those on Business/Enterprise plans can choose to set-up via CNAME). Nameservers usually take time to propagate, this can be 24-48 hours (where as A records or CNAME records usually have a much lower TTL).
You can check which nameservers your computer is pointing to on a Mac/Linux box by:
dig NS
On Windows you can do:
nslookup -type=NS
This will tell you the nameservers you computer is pointing to, and whether you need to wait longer for them to propagate to CloudFlare.
Long story short, just be patient. :)
Use the google dns 8.8.8.8 and 8.8.4.4 in your client IPV4 connection properties. It might be that your ISP is caching the site and you are not able to see the instant changes
Related
so I've followed the documentation of Amazon's S3 and Route 53 to host a static website.
it worked perfectly and the next day my site was online. I kept updating my index.html afterward with small stuff like extra Text here and there and so far I had no issues, it would every time update the site to reflect the new changes. Until suddenly I visit my website and get a "server IP address could not be found" and I cannot reach my website.
I checked dnschecker.org and internic.net to verify the DNS status of my site, and it showed everything green. I created an Availability test in the Route 53 dashboard and it returns 200 OK.
I also made sure the 4 server names from the Hosted Zone match the ones internic is returning.
so apparently every service says that my site is reachable, but it's not. I have not changed any Public Access options since the first time after I've initially done it using the documentation.
I have also tried reaching the site from a different browser, different PC, and from my phone. they all cannot reach the website.
I absolutely have no idea what to do, to get my site back running. I would very much appreciate some insight.
Footnote: I am very new to this, so please let me know if I need to provide extra information
so it turned out the reason is that I was on the college's Network and somehow my website got delisted from their DNS server (I don't have an exact explanation, just an observation).
my website loaded using Data on my phone and also if I turned on a VPN on my PC. so basically its a DNS problem
I am trying to create a GitHub page for a repository. But when I gave the custom domain name, it shows the following message "Domain's DNS record could not be retrieved. For more information"
As I am new to GitHub I am not getting the information what is documented in GitHub pages. Could anyone help me to resolve this problem?
If you've recently changed or removed your custom domain and can't access the new URL in your browser, you may need to clear your browser's cache to reach the new custom domain. For more information on clearing your cache, see your browser's help site.
In order to serve the Page, your DNS records must point to GitHub's server. To confirm that your custom domain points to GitHub's servers, use the dig command with your custom domain. The dig command shows you where your custom domain points. For example:
$ dig example.com +nostats +nocomments +nocmd
example.com. 3600 IN A 185.199.108.153
In the example above, example.com points to the IP address 185.199.108.153.
If you configured A records through your DNS provider, your A records must point your custom domain to the following IP addresses:
185.199.108.153
185.199.109.153
185.199.110.153
185.199.111.153
You may see a different IP address, since we serve Pages with a global Content Delivery Network. Use dig username.github.io to see the full resolution path. Note that DNS caching may cause a delay.
If you're using an A record that points to 192.30.252.153 or 192.30.252.154, you'll need to update your DNS settings for your site to be available over HTTPS or served with a Content Delivery Network. For more information, see "HTTPS errors."
If you're using an A record that points to 207.97.227.245 or 204.232.175.78, you'll need to update your DNS settings, as we no longer serve Pages directly from those servers.
Source: https://help.github.com/en/articles/troubleshooting-custom-domains
Route 53 Issue? server DNS address could not be found.
Everything was working fine until this morning. I bought from amazon a few weeks back and had deployed a personal webpage, no issues. Today, I made a small change and added a favicon to the page. Then I redeployed, everything is working. http://34.211.101.154/
Now I'm having issues with route 53. I've checked and double checked my name servers (ns) to make sure that the registered ns match the hosted ns. I have a health check running and it shows that all the endpoints terminate with a success 200.
Success: HTTP Status Code 200, OK. Resolved IP: 34.211.101.154
But still, when i go to the domain name, the request won't resolve on wifi but it is okay on LTE. Does anybody know the issue? Please help!
Perhaps the wifi router you're using has cached some DNS configuration. Try resetting the router or using a different wifi network to test the issue.
Actually, turns out everything was working fine. It's just AWS needed time to process the request... I waited like 2 hours and it started working. Thanks
I created this question earlier but was told that it is a DNS issue as apposed to an issue with HSTS. Regardless, here is what I need help troubleshooting:
Issue:
A single site (one that I own), is showing server DNS address could not be found. DNS_PROBE_FINISHED_NXDOMAIN when I try to connect to it via chrome, firefox, or safari. I can however connect to it via Tor Browser. I can also verify that the address resolves correctly using mxtoolbox. I also am not able to connect via two other computers and two other phones. I also am not able to connect via a different WIFI connection or personal hotspot via my phone. Curl and Host via the command line are also not able to get a response.
What I've tried:
As I said above, I've tried different internet connections and computers. I've also tried flushing my DNS cache and pointing to another DNS server.
Having said that, I am not sure how else to trouble shoot this. The only change I made to the web app was to add HSTS headers, hence why I created the earlier posing. Please let me know what other information I can provide. Otherwise, here are some details about the site itself:
Other information about my stack:
Django web app
Gunicorn / WSGI server
Hosted on Heroku - Cedar-14 stack
DNS setup with AWS route53
domain name registered through AWS
EDIT:
Possibly related: https://serverfault.com/questions/606880/how-can-i-troubleshoot-a-route-53-hosted-zone
I had the similar issue and was not able to open Facebook. Rest all sites were working fine. Initially, I thought Facebook blocked me as I never faced this crappy issue earlier. Later when I searched in Google, I found an article which described the DNS_PROBE_FINISHED_NXDOMAIN issue on Chrome.
I just changed my DNS server address as 8.8.8.8 (preferred) and 8.8.4.4 (alternate) and I never faced that issue again.
Reference - https://www.mobipicker.com/dns_probe_finished_nxdomain/
So from our discussion regarding the NS server records always make sure that the local NS records matches the Parent NS records.
In your case there there were 2 extra NS records associated with your domain that was the reason why your domains and sub domains were acting unhealthy. once you deleted those records the domains and sub domains were back to normal.
you can also try to open an anon window
access the url
use it in anon mode
or
close it and it will load ok
I have my non-www domain.com with GoDaddy and my WordPress Blog is hosted in AWS EC2. I'm using Route 53 to handle DNS requests. The existing solution for my question, seen in many places(including SOF) is to create two S3 buckets in the name of non-www domain and www domain for redirection of static websites. This is not my case.
I've my WordPress installed in EC2 and not using S3 for holding my Data. I hope this is not a static website and cannot follow the general solutions available.
I tried the following solution around and did not work
I tried changing the C-NAME record to www.domain.com but it did not worked.
I tried domain forward feature available with GoDaddy.com and didn't work.
I tried modifying .htaccess file and that too didn't work.
This is what my record sets in Route 53 look like
Name Type Value TTL
------ ----- ----- ----
domain.com. A xx.xx.xxx.xxx (EIP) 300
domain.com. MX 1 ASPMX.L.GOOGLE.COM 3600
5 ALT1.ASPMX.L.GOOGLE.COM
5 ALT2.ASPMX.L.GOOGLE.COM
10 ALT3.ASPMX.L.GOOGLE.COM
10 ALT4.ASPMX.L.GOOGLE.COM
domain.com. NS ns-27.awsdns-03.com. 172800
ns-1190.awsdns-20.org.
ns-2028.awsdns-61.co.uk.
ns-855.awsdns-42.net.
domain.com. SOA xxxxxxxxx 900
How can I redirect my domain.com to www.domain.com?
I was hesitant to post my comment as an answer because there are a gazillion ways to setup and configure Wordpress it seems. Anyway, to keep in the spirit of keeping this question in the amazon-web-services tag I ran a test case deploying from the AWS Wordpress Cloudformation template. I'm not sure if this is how you actually installed Wordpress but here is one way to redirect:
Make sure that your Cloudformation template completes successfully.
Here is what my Hosted Zone looked like - I have not added A records yet.
Get the instance IP address. Note that in this example I did not setup an Elastic IP. Since I knew that I would not need to stop the instance temporarily I opted to just stick with the automatically assigned, random pubic IP.
Next I made an A record for the domain apex of that IP and then an A record for www. I also changed the TTL to 60 seconds.
Once DNS propagation completed I tried accessing my domain name. As you can see, the AWS Cloudformation Wordpress installation defaults to a different path and URL.
Using the URL, http://example.com/wordpress did the trick.
I didn't go through the steps but when you go to http://example.com/wordpress it starts a setup screen. Enter all the information like DB name and password, etc. and then login to the admin panel. Once you go through all of that you go to the General settings screen. This is where your configuration will probably be different but for mine, the URLs were listed as http://example.com/wordpress. I simply changed these URLs to http://www.example.com/wordpress. (As an aside, I also tried changing and saving the permalink section to generate an .htaccess file but one was not generated due to the inability to write to the file. I tried making my own but I kept running into "too many redirect" messages so this might not be a route you want to take depending on your install.)
You will need to make a change in the index.php file. For my installation it was located at /var/www/html/wordpress/index.php. Make sure to make a copy before changing it. I simply added /wordpress/ in front of wp-blog-header.php. Again, this install puts the Wordpress files in the directory /wordpress - your install will probably be different.
Next you need to copy that modified index.php file to /var/www/html/ and then restart the httpd service.
To test the change I cleared out my DNS cache and opened up the network section of developer tools in Chrome.
I then opened a new tab (have to open developer tools again) and then typed in the naked domain name.
As you can see, the URL redirected to www.example.com with a 301 permanent redirect.
I'll through another suggestion out here while I'm at it. You can use the free version of Cloudflare to just do the redirect for you. Cloudflare offers a bunch of other free and useful services like CDN so if you don't mind depending on a 3rd party service (a reputable one by the way) it might be easier with more value add. As I highlighted in the screenshot however, note that if you use forwarding you cannot use some of the other advanced rule sets.
Anyway, I hope this helps!