Reducing DNS caching

Saleem N. Bhatti*, Randall Atkinson

*Corresponding author for this work

Research output: Chapter in Book/Report/Conference proceedingConference contribution

Abstract

Motivated by our ongoing work exploring an alternative Internet architecture, we wish to make use of naming services in order to support functionality such as: host and network mobility; application and/or virtual machine migration; and various forms of traffic control (e.g. multi-homing). Currently, the Domain Name System (DNS) is used to resolve names to DNS records, with relatively large time-to-live (TTL) values (several thousands of seconds) for caching the results. To support new agile services and systems, cached results may need to have much lower TTL values, so that cached DNS values do not become stale as system changes occur, e.g. changes to end-system location information to support new methods of mobility. However, current conventions for DNS configuration normally use conservatively high TTL values. We have conducted an empirical study of a live DNS deployment where we have reduced to zero the TTL values of records for the entire School of Computer Science at the University of St Andrews. Our results show that the increase in DNS load is much lower than might be expected, following a highly non-linear decrease with respect to the TTL value of the DNS records.

Original languageEnglish
Title of host publication2011 IEEE Conference on Computer Communications Workshops, INFOCOM WKSHPS 2011
Pages792-797
Number of pages6
DOIs
Publication statusPublished - 26 Jul 2011
Event2011 IEEE Conference on Computer Communications Workshops, INFOCOM WKSHPS 2011 - Shanghai, China
Duration: 10 Apr 201115 Apr 2011

Publication series

Name2011 IEEE Conference on Computer Communications Workshops, INFOCOM WKSHPS 2011

Conference

Conference2011 IEEE Conference on Computer Communications Workshops, INFOCOM WKSHPS 2011
Country/TerritoryChina
CityShanghai
Period10/04/1115/04/11

Fingerprint

Dive into the research topics of 'Reducing DNS caching'. Together they form a unique fingerprint.

Cite this