I have bought my domain from one domain registrar and set domain forwarding to where my website is hosted. Now I have setup my website on amazon cloud and did all changes as described and changed DNS changes from my domain registrar.
Everything works good from IE and even from inbuilt browser of Eclipse. But Firefox is still taking to the site where site was hosted earlier.
what is the reason and how to resolve? I have cleared the cache related to website.
Perhaps these links may be of help:
Firefox invalidate dns cache
http://en.kioskea.net/faq/555-disabling-the-dns-cache-in-mozilla-firefox
Related
So I have a rails multi-tenant project running on Heroku where we identify what to serve based on the domain you access from. These domains are added to the app's heroku domains and the cname records provided by Heroku for www.domain.com are added to the domain's DNS and we also add a permanant redirect rule for domain.com/* -> www.domain.com/$1 so that people can access without a www.
This all works perfectly fine on Chrome/Firefox, but on Safari and IOS devices we've been getting reports and were able to reproduce that the websites simply timeout.
I have tried to monitor traffic with wireshark, I can see the GET HTTP request going out but nothing comes back.
I have tried to access the app directly using the appname.herokuapp.com URL, it works perfectly fine in that case.
I have tried accessing with a VPN (Cloudflare WARP), the issue is not present in this case. However I tried manually setting the DNS to Cloudflare's and that did not fix the issue. I have also tried 3 different ISPs and that was also not the issue.
So to sum up, the issue happens if:
You're accessing using a domain that POINTS TO a CNAME record (xxx.herokudns.com) that POINTS TO the app.
You're not using a VPN/Cloudflare WARP.
You're on Safari.
I have found a reference for this issue here but this dates back to 2015. I also have doubts that this Safari update could be relevant.
Has anyone been through this previously or can provide insights on to how I can further debug this?
I've looked at this answer and it doesn't solve my problem.
I just switched to a new site builder. Previously I was using Kajabi. Now i'm using GroovePages (GP). I switched DNS Settings in GoDaddy to GP's custom DNS servers, but now I am seeing 2 different websites when I go to the WWW version and the NON-WWW version of my website. The NON-WWW is correctly showing the page i built on GP, whereas the NON-WWW is not.
To make a long story short, I've been through long email threads with each company and seems like neither one knows how/why the WWW is not properly routing to the new site. GroovePages claims they have proper CNAME record set, as they are the ones managing the DNS records. Kajabi claims to have reset any lingering records also.
Currently the WWW version is pointing to Heroku, but I don't even have a Heroku account and haven't used them to host my website.
How do I fix this problem?
You need to make sure when you setup Forwarding that you forward to www.mysite.com instead of mysite.com
Link to forward my domain: https://in.godaddy.com/help/forward-my-domain-12123
I use Cloudflare as a DNS server for my website.
for example, I defined www.mydomain.com, landing.mydomain.com to point to a Google Cloud CDN storage bucket IP in which I serve my static landing files.
the problem is when I deploy a new version of my code on that bucket, even after time passes more than the cache TTL of that bucket, I see my old landing on my domains, specifically on my www subdomain.
when I use another DNS server like DNSimple, the problem resolves.
I think the problem is with the Cloudflare caching system.
I went to the Caching part of my domain’s configurations in the Cloudflare panel, purged entire caches, and set the Development mode “ON” and also set the “Always Online” part “OFF”.
but the problem remains.
I’d be very delighted If anybody could tell me what should I do to get rid of the cache!
When I updated my website on my tower pc, Firefox and chrome do not update the result they remain on the domain providers Parked webpage. However, Opera does update an goes to my server and all is working well. But only with Opera.
So I get off my tower pc as I thought it was a cache issue on my machine.
I go on a mobile internet device using the same virgin superhub router but this time via wi-fi, and again firefox and chrome do not show the updated website result but Opera does.
so the same result on both tower and mobile. Indicating perhaps this is not a cache issue on my browsers.
It's like my ISP or domain provider is caching firefox and chrome, but Opera is bypassing this cache and going to my server as it should?
please help!
Most likely:
Your router has cached the DNS settings of the holding page, so any request going out from your LAN will get directed to the old IP address.
Opera could be configured to use a proxy which has been a feature of the mobile apps for a long time and was added to desktop Opera a couple of years ago. This would bypass your local DNS server.
When the TTL of the old DNS expires, you could get the new site.
To those on virgin media super hub. it finally worked. the DNS settings cache cleared.
I believe it took approx 48 hrs ( hard to tell exactly)
so if you buy a domain you have been viewing(viewed its parked page),you may be able to use Opera browser sooner as it does not use the routers dns cache if set up as a proxy. And also you can use a proxy website to view your domain online. You may be able to reset your router to clear the cache? I did not want to lose my settings, so I waited. It just takes some time on firefox chrome and perhaps a few other browsers (on the router you have recently viewed the domain) as these browsers rely on the dns cache on the router.
From what I gather.peace :)
I have recently hosted my site which intends to use wildcard subdomains in its general use. A user would go to account.website.com to access their part of the site. The site is a rails app hosted on heroku and domain is through 123-reg. DNS is set up as per heroku - * , cname , wildcard.app.heroku...
At first i thought 123-reg couldnt handle wildcard routing and i would have to change dns provider as whenever i go to account.website.com it will send me to www.account.website.com which is extremely irritating, but then i found that this does not happen on my windows machine, only on my dev machine (macbook pro). In both cases i am using Chrome. Firefox works as desired, only chrome is messing up.
Any insight into why this is happening would be fantastic.
Thanks
Obviously i immediately solve it after asking and look like a fool - Apparently the cache remembers the redirect from when i assume i hadnt yet set up dns correctly. If you get the same problem, clear browser cache