Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I went to my zoneedit.com, changed mydomain.com to point to a different IP. But changes haven't taken affect yet.

Is this because my ISP DNS is caching?

share|improve this question

6 Answers 6

up vote 12 down vote accepted

Yes. Your ISP is almost certainly caching DNS settings for some period of time. They are supposed to refresh the records when the TTL expires. Unfortunately there are a large number of ISPs that seem to ignore TTLs all together in their DNS caching schemes. If you happen to be on one of those ISPs it could be hours or even days before they respect the new records, even if you have a very low TTL set.

share|improve this answer

I faced the same issue and fixed it via using google DNS

Open your Network /IP settings Use DNS servers as:

8.8.8.8
8.8.4.4

These are google DNS and will solve your prob until ur ISP refresh the catche enter image description here

share|improve this answer
    
Excellent temporary fix. One can simply switch to Google's DNS servers for a day or two until their stupid ISP (which doesn't respect the TTL) clears the DNS cache. I am using this, and it worked great. Thanks a lot! –  its_me Sep 28 '12 at 6:52
    
Excellent Fix..Thanks for the solution. –  Fahid Mohammad Jul 3 '13 at 3:30

Alex:

Yes. Your domain's DNS record specifies a TTL ("time to live") value, which directs client computers (and ISP nameservers) to cache results for a specified length of time before asking again. Default values of 24-48 hours are typical.

Here's one good practice for making future transitions go more smoothly: go in a few days ahead of your cut-over date and change the TTL to something very short, e.g. 300 seconds. When you configure the new IP address, you can set it back to 24 hours. From your perspective, the chief benefit of a long TTL is that your site's visitors will experience the performance benefit of cached DNS queries. It also lightens the load on your domain's nameservers.

In light of your current situation, you may want to explore the possibility of continuing to mirror your content for a few days at the old address (if your site is static) or configuring the HTTP server at your domain's old IP address to refer requests to the new IP address (if your site is dynamic).

Cheers,

Miles

share|improve this answer

There are two things here. One is the time it takes for your domain registrar to place the DNS entries you've provided through some sort of web form / management panel on the registrars DNS servers. This 'update' process usually occurs within 15 minutes.

Two there is the TTL field of each RR (Registry Record), which basically says: if someone asked about domain.com before, cache the domain.com -> IP address RR for TTL seconds (cache so I don't have to ask an authoritative server again / every time some host asks about domain.com). TTL values vary, usually they are set to about 1 day == 86400 seconds.

You can actually check if the DNS server of your ISP cached the result, by asking the ISP DNS server explicitly, using the commands:

nslookup domain.com ns1.isp.com
dig domain.com @ns1.isp.com

The TTL in the response field will indicate for how much time the RR is cached on the server.

share|improve this answer

Your ISP runs a DNS server that is caching DNS entries for as long as you tell it to.

If you control a DNS record, one aspect of that record is the "TTL" which tells DNS servers (and properly behaving clients) how long it should cache that value after it gets it from the authoritative DNS server.

Please note -- there is a tremendous distinction between your ISP and your ISP's DNS server. There is nothing forcing you to use your ISP's DNS server. You can run a recursive server yourself, you can use google's DNS servers, you can use OpenDNS.

Also, if you're expecting to change your DNS records often, and you want those updates to take effect quickly, you should reduce the TTL of your records. You'll see more load on your DNS server, but at the same time, your DNS chages will be seen faster.

share|improve this answer

It takes up to 72 hours for zone record updates to complete propagating worldwide. And yes your ISP caches DNS queries

Edit: There are a number of online tools you can use to track the progress of the update. Check out this one.

share|improve this answer
1  
@Iraklis: This is incorrect. You're "propagating" a myth. DNS records don't propagate, they cache. They cache for the TTL of the record in question, not 72 hours, unless the TTL is 72 hours. –  joeqwerty Apr 5 '10 at 11:07
7  
@joeqwerty, in @Iraklis's defense, that is something of a matter of perspective. The records aren't being actively pushed out, it is true, but one could call the process of caches expiring and fetching fresh records propagation. From a certain point of view. Eg entry 7 on wiktionary en.wiktionary.org/wiki/propagate –  dsolimano Apr 5 '10 at 13:05
1  
@dsolimano: No offense, but I don't agree. No matter how you look at it, the word propagation has a specific definition that is not open to interpretation. His "perception" that DNS records propagate and that this propagation takes 72 hours is incorrect, and espousing such an idea only acts to further a commonly stated falsehood on how DNS works. –  joeqwerty Apr 5 '10 at 13:29
4  
I still feel the term "propagation" describes how DNS records get updated better, even if it doesn't mean technically pushing values. Anyway, but thats just me. –  Iraklis Apr 5 '10 at 13:43
1  
Propagation works very well as a term that generally non-technical users seem to understand. –  ceejayoz Jan 4 '12 at 20:11

Your Answer

 
discard

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.