It depends on the nameserver asking the question.<br><br>The authoritative nameservers (master/secondaries) are going to instantly give the correct answer as soon as you change it. If a remote DNS server asks, it's first going to consult its cache, and failing that, recursively resolve the name. If the record is in the cache, it won't change until the record times out**. If it isn't, the correct answer is returned instantly.
<br><br>So, how to find out if it's cached? Our friend dig to the rescue:<br><br># dig <a href="http://ertw.com">ertw.com</a> @<a href="http://ns1.ertw.com">ns1.ertw.com</a><br><br>; <<>> DiG 9.3.1 <<>>
<a href="http://ertw.com">ertw.com</a> @<a href="http://ertw.com">ertw.com</a><br>; (1 server found)<br>;; global options: printcmd<br>;; Got answer:<br>;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8220
<br>;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0<br><br>;; QUESTION SECTION:<br>;ertw.com. IN A<br><br>;; ANSWER SECTION:<br><a href="http://ertw.com">ertw.com</a>. 4079 IN A
<a href="http://24.79.141.139">24.79.141.139</a><br><br>;; AUTHORITY SECTION:<br><a href="http://ertw.com">ertw.com</a>. 7200 IN NS <a href="http://ns14.zoneedit.com">ns14.zoneedit.com</a>.<br><a href="http://ertw.com">
ertw.com</a>. 7200 IN NS <a href="http://ns12.zoneedit.com">ns12.zoneedit.com</a>.<br><br>You can see that the A record for <a href="http://ertw.com">ertw.com</a> has been cached locally -- the ttl is 4079 seconds as of my query. However the 2 NS records were not cached, so they are pulled from the authoritative server and now have a 7200 second lifetime. I'll ask again in a few seconds (just the relevent lines posted)
<br><br><a href="http://ertw.com">ertw.com</a>. 3898 IN A <a href="http://24.79.141.139">24.79.141.139</a><br><a href="http://ertw.com">ertw.com</a>. 7019 IN NS <a href="http://ns14.zoneedit.com">
ns14.zoneedit.com</a>.<br><a href="http://ertw.com">ertw.com</a>. 7019 IN NS <a href="http://ns12.zoneedit.com">ns12.zoneedit.com</a>.<br><br>As you can see, the server continues to count down. It's not for another 3898 seconds that my local server would notice that
<a href="http://ertw.com">ertw.com</a> has changed.<br><br>** Some DNS servers have been known to ignore the TTL on a record and make up its own value. I've only run into this when setting absurdly low TTLs (< 300s) but I wouldn't be surprised if there were some that always ignored it.
<br><br>Sean<br><br><div><span class="gmail_quote">On 12/18/06, <b class="gmail_sendername">Montana Quiring</b> <<a href="mailto:montanaq@gmail.com">montanaq@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hello,<br><br>I'm interested in hearing what people's experiences are.<br>When changing the IP of a (web) server on the Internet, how long does<br>it take to DNS to propagate?<br><br>-Montana<br>_______________________________________________
<br>Roundtable mailing list<br><a href="mailto:Roundtable@muug.mb.ca">Roundtable@muug.mb.ca</a><br><a href="http://www.muug.mb.ca/mailman/listinfo/roundtable">http://www.muug.mb.ca/mailman/listinfo/roundtable</a><br><br></blockquote>
</div><br><br clear="all"><br>-- <br>Sean Walberg <<a href="mailto:sean@ertw.com">sean@ertw.com</a>> <a href="http://ertw.com/">http://ertw.com/</a>