When Does World IPv6 Day Start?
Almost all users access websites by using the name of the webpage. Typically, the user's web application (such as a browser) will send DNS queries to a caching DNS resolver which is provided by the user's ISP. The caching resolver will do recursive queries to find the address of the website, return the answer to the user, and also cache the answer. If another user asks for the same website's address, the resolver doesn't have to go looking for the answer; it already has it in its cache.
Figure 1 shows the values for negative caching of DNS resource records for websites listed in ISOC's list of World IPv6 Day participants, on 30 May 2011. The negative caching values we found include 60 seconds at the low end. Other frequently recurring values are 5 minutes, 1 hour, 2 hours, 1 day and 2 days even! If in the upcoming week these values don't change, a substantial fraction of websites could still be seen as single-stacked up to an hour after they publish both A and AAAA records. Some websites may not be visible to some users for a full day or more! However, we expect a lot of the participants to lower either the minTTL value in the SOA, or the TTL on the SOA itself in the coming days, so the effect of negative caching remains minimal.
Note that BIND has an option called max-ncache-ttl , which defaults to 3 hours. This prevents most standard BIND resolver installations from caching negative responses for more than 3 hours. This helps to work-around the large negative caching TTL values that some zones publish.
In this article we look into how DNS negative caching affects the start of World IPv6 Day, which is something World IPv6 Day participants should be aware of. We show that with the current settings, some World IPv6 Day participant can expect caching to happen for multiple hours. We hope that people that currently have long negative caching periods had planned to change DNS settings in the coming days, if not, it's not too late!