Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I was looking after the frequency of dns updates, since I had to change the location fo the vps that hosts the domain contents. What I ussualy read is that it takes up to 72 hours to get these changes propagated, sometimes this can be sooner based on your location.

I changed the nameservers for the domain about a week ago. When I ping the domain name from different locations it still points the old vps (which does not exist anymore).

I was wondering if its normal that it can take this long for the change to point my new vps? If I might have done something wrong here, where should I look for it (it looks all ok, when I check it). If it is reachable from your location (if so, its probably a matter of time it will propagate to my location).

share|improve this question

DNS frequency is based on the TTL settings of a zone file which has authorized ownership of that domain. Lowering the TTL and then incrementing the serial number with the zone file followed by a refresh will push changes to propagate however they will also update as frequently as what is specified within their own refresh intervals.

As a rule of thumb generally what I recommend is lowering the TTL at least 24 hours in advance before making changes in a host and then changing it back to original defaults later on in time.

TTL stands for time to live, i'm not sure what the best practice interval is at for ideal settings however usually a default of 24 hours is comforting area to be at.

share|improve this answer
Outside of the zone transfers that happen amongst a certain DNS zone's nameservers, there's no "push" or active propogation in DNS. The only thing one can do is wait for caches to expire and then remote resolvers will fetch a new record from the authoritative servers for the domain. But yes, you're right, lowering TTL will help speed this process along. Just wanted to be clear that you can't "push" out your DNS changes. DNS is largely a "pull" system. – EEAA Oct 29 '10 at 20:12
Hi, although I am not completely sure anymore, I think it was set to 14400 before the change (4 hours). However I am waiting for at least 6 days for it to happen. – Roderik Oct 29 '10 at 20:14
However, does the domain name resolve at your location? – Roderik Oct 29 '10 at 20:17
I'm getting these results. Non-authoritative answer: nameserver = nameserver = – Nick O'Neil Oct 29 '10 at 20:21
These nameservers are correct. That should point you to: if I am right. Does it go there at your place? – Roderik Oct 29 '10 at 20:51

What I ussualy read is that it takes up to 72 hours to get these changes

Well, what I can say is don't read crap, you'd better prefer RFCs.

DNS is all about caching. If you need small latency for your records change then use appropriate TTLs for your DNS-records (yes, they are set per record, not file, actually).

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.