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

Whenever I make changes to DNS I have noticed that it takes hours to propagate when viewing from my wired connection but with minutes I can see the changes reflected when browsing on my mobile, 3g T-mobile network.

I really would like to understand why this happens.

With regards to the question being closed: The question is fine. Closing it for not being "relevant to professional system administration" is both incredibly annoying and incorrect.

Is this due to the terminology I used in the question or the content?

share|improve this question

closed as off-topic by pauska, ceejayoz, mdpc, Ward, MadHatter Dec 9 '13 at 14:30

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions must be relevant to professional system administration. Server Fault is dedicated to professional system and network administrators. End user and enthusiast questions are off-topic (contact your system administrator or hire a professional to help you out). Please see the Help Center for more information." – pauska, ceejayoz, mdpc, Ward, MadHatter
If this question can be reworded to fit the rules in the help center, please edit the question.

It depends on the cache retention policy of the DNS server you're using on those devices. Some will keep a record for a day, some will cache nothing, etc... – mveroone Dec 6 '13 at 15:04
up vote 4 down vote accepted

DNS records have a TTL (time to live). This in seconds and can be anywhere from 0 to weeks.

dig     300 IN  A

In this case the TTL is 300 seconds and a conforming server will only keep the record for 300 seconds before refreshing it. Unfortunately, DNS records get cached in many different places and not all software does the correct thing wrt honoring the TTL. Web browsers are notorious for this, but the worst offender I know of is the nscd daemon on linux systems.

It can often be quite difficult to figure out exactly which piece of software is holding on to out of date records.

share|improve this answer
IPv6 may have something to do with this – rjt Dec 9 '13 at 16:58

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