DNS propagation delay: An effective and robust solution using authoritative response from non-authoritative server

Abstract

DNS Servers significantly play a vital role in Internet and Intranet environments. It translates humanfriendly names into IP addresses and vice versa. However, propagation processing of any change in DNS Server takes hours and days for its full global-wide implementation in both the versions of IP addressing scheme. This is the age of fast communication where bulk of data communication occurs globally in terms of tera, peta or exa bytes etc., where trends of developing traditional desktop software changing into dynamic web-based applications, where computer networks are emerging into telecommunication networks, where wired and wireless networks are transforming into network mobility, where traditional data communication is emerging into highspeed digital audio/video streaming using video conferencing IP data streaming techniques; it sounds contemptible and abominable for waiting hours for DNS information proliferation for a single minor change. In this paper, an authoritative response from a non-authoritative DNS server is proposed and tested, through which not only request time out has been reduced but also DNS resolution time dropped to around 50% in comparison with the existing DNS resolution process.

A global name service for a highly mobile internetwork

“…DNS's heavy reliance on TTL-based caching, a key strength recognized by its creators, researchers, and operators alike, poses a significant handicap by increasing update propagation delays, load on name servers, and overall client-perceived latency. It is not uncommon for DNS update propagation to take a day or more, resulting in long outage times when online services have to be moved unexpectedly, prompting cries for help on operator forums [7,47]. A less widely noted limitation of DNS is its reliance on hierarchical names for scaling via federation and its single root of trust, which constrains mobile applications from selecting arbitrary application-specific names (as elaborated in §2.2 and §3.2).…”