Results 1 to 5 of 5
Thread: DNS Propagation
-
10-01-2015, 09:15 AM #1Newbie
- Join Date
- Oct 2015
- Posts
- 7
DNS Propagation
Hi,
I think I have the worse scenario or what?
It has been almost 72 hours.
NS redirected, and the websites work when i checked them with proxy, and showing the new NS and IP on Whois page.
But most of the users see offline page, it's not working for them.
What do you think about that?
The domain is on Godaddy and I created host dns ns1.domainname.com and IP address, ns2.domainame.com and IP address. After that, i changed the NS addresses. Redirected to new NS within an hour. But the websites are still offline for users. Just one hundred twenty percent users connect to the website.
-
10-01-2015, 09:23 AM #2Newbie
- Join Date
- Dec 2013
- Location
- /root
- Posts
- 22
Whats is domain name?
Grupo INDAX™®
Shared & Reseller Hosting, Streaming Audio/Video, VPS Managed & Dedicated Servers.
5 Locations: Santiago de Chile (Chile), Chicago, IL (US), Dallas, TX (US), Los Angeles, CA (US), Miami, FL (US).
-
10-01-2015, 04:16 PM #3Newbie
- Join Date
- Oct 2015
- Posts
- 7
For your information,
It was about nginx 1.9.4;
*) Change: now nginx checks the whole cache key when returning a response from cache.
Fixed the issue with nginx 1.9.5
-
10-01-2015, 04:55 PM #4Mostly Retired!
- Join Date
- Nov 2002
- Location
- Portland, Oregon
- Posts
- 2,992
Nice find! Also, thanks for coming back and sharing your fix. Always a good thing.
-
10-01-2015, 08:05 PM #5Web Hosting Master
- Join Date
- Dec 2011
- Posts
- 1,460
DNS does not actually propagate. We call it that because we lack a better word to describe the process. Propagate implies a "push" style update when in fact it's a "pull".
Name servers will update their cache entries when they update - and there's nothing either you or your DNS provider can do to force them to update any sooner than that.
The only thing you can and should do is prior to any DNS change you know in advance you're going to be making is to go in and lower the TTLs on all your resource records to something absurd, like 300 seconds. That should be done at least a week in advance. Then when you do go in and change your DNS records, the wait for everyone to update their cache entries is nowhere near as long.
If you're changing GLUE records at the registry though - that's a special kind of hell because the TTL on those entries is typically 7 days."I've seen spam you people wouldn't believe. Routers on fire off the OCs of AGIS. I watched MXes burning in the dark near the Cyberpromo Gateway. All those moments will be lost in time, like tears in rain. TTL=0."
Similar Threads
-
DNS propagation question
By kreativ in forum Web HostingReplies: 10Last Post: 07-01-2002, 06:03 AM -
H-Sphere - Can you view pages before DNS Propagation?
By JustinSurfer in forum Hosting Software and Control PanelsReplies: 5Last Post: 03-28-2002, 11:37 AM -
DNS Propagation, slower than usual.
By Synergy in forum Domain NamesReplies: 2Last Post: 03-22-2002, 11:54 AM -
average time for DNS propagation?
By Fayte in forum Web HostingReplies: 13Last Post: 05-12-2001, 12:45 PM -
DNS Propagation
By MilkMan in forum Web HostingReplies: 11Last Post: 09-09-2000, 04:28 AM