Home / Blogs

DNS: An Essential Component of Cloud Computing

The evolution of the internet is anchored in the phenomenon of new technologies replacing their older counterparts. But technology evolution can be just as much about building upon what is already in place, as it is about tearing down past innovations. Indeed, the emergence of cloud computing has been powered by extending an unlikely underlying component: the more than 30-year-old global Domain Name System (DNS).

The DNS has offered a level of utility and resiliency that has been virtually unmatched in its 30-plus years of existence. Not only is this resiliency important for the internet as a whole, it is particularly important for cloud computing. In addition to the DNS’s resiliency, cloud computing relies heavily on DNS capabilities such as naming schemes and lookup mechanisms for its flexibility, usability and functionality.

Historical Perspective

As far back as the original ARPANET (the precursor of the internet), communication endpoints have had both names and addresses. The association between the two was originally recorded in the classic HOSTS.TXT file, where a master copy was kept in a centralized server and copies were distributed to endpoints. Making updates to the ARPANET’s HOSTS.TXT was originally a fully centralized function coordinated by Stanford Research Institute; while the actual use of the file to lookup names and map them to network addresses was a local function, implemented within the endpoint.

That started to change in the 1980s, when Paul Mockapetris proposed the DNS, replacing HOSTS.TXT with a hierarchical naming system, with management of different parts of the overall namespace “delegated” to different endpoints. As Mockapetris noted in his design principles, “The sheer size of the database and frequency of updates suggest that it must be maintained in a distributed manner, with local caching to improve performance.”

Emergence of Name Servers

Due to the delegation of authority, an organization could update the name-address mappings for endpoints within the organization locally without having to change the master file. But the trade-off was that lookups could no longer be implemented solely as a local function since no one had a copy of the entire file anymore.

Instead, the sending endpoint would need to interact with an “authoritative name server” for the receiving organization to get the network addresses for endpoints within that organization. And to identify the receiving organization’s authoritative name server, the sending endpoint would also need to interact with other name servers—starting with the newly defined DNS “root” servers.

Specialized computers were set up within organizations (or by their internet service providers) to perform the (now iterative) resolution process of navigating from the root to top-level domains (TLDs) and onward to the endpoint’s authoritative name server. Endpoints within the organization would then “outsource” their lookup process to the specialized servers, which were designated as recursive name servers.

Relationship Between the DNS and Cloud Computing

Like other parts of an organization’s IT infrastructure, recursive name servers can be moved from on-premise deployments into the cloud. In fact, some organizations now contract with network operators and other service providers for their recursive DNS services; this external outsourcing of DNS resolution is like an external cloud deployment, providing “DNS resolution as a service” or “Cloud DNS.” Organizations have likewise outsourced their authoritative name servers to external service providers.

But this isn’t the only relationship that the DNS has to cloud computing. The DNS also plays an important role in enabling other cloud services. Indeed, resources in cloud computing platforms are generally identified with domain names and located by DNS lookups.

For example, Amazon Web Services recommends that “buckets” of objects—the basic unit of storage in its Simple Storage Service (or “S3”)—be named according to DNS naming conventions. An appropriately named bucket can then be accessed via a Uniform Resource Identifier (URI), such as: “http://myawsbucket.s3.amazonaws.com/yourobject”. Following standard DNS processing, a browser or application would then resolve the URI into a network address for the virtual server that hosts the bucket.

Similar naming conventions can be found in other cloud services, such as Microsoft Azure Storage (e.g., “http://mystorageaccount.blob.core.windows.net/mycontainer/myblob”) and Google Cloud.

Importance of DNS-based Conventions in Cloud Computing

A DNS-based naming scheme—and consequently a DNS-based lookup mechanism—can take advantage of the capabilities built into the DNS to balance application workload across multiple servers. These capabilities are fundamental to rapid elasticity, one of the National Institute of Standards and Technology (NIST)‘s five characteristics of cloud computing. In particular, a domain name can provide a “virtual name” for a resource in a cloud platform—resource instances corresponding to the name can then be deployed at many different physical locations. This gives the effect, as described by NIST, that “the capabilities available for provisioning often appear to be unlimited and can be appropriated in any quantity at any time.”

The DNS “function” of mapping a fully qualified domain name to a network address—a function implemented by an authoritative name server for the cloud platform—is thus a fundamental building block for cloud computing. Indeed, in order for endpoints to interact reliably and confidently with named resources on the cloud platform, the platform’s name server must be available and accurate.

This principle continues up the DNS hierarchy all the way to the root. Authoritative name servers themselves have domain names, and the mapping between a name server’s names and actual server instances is also managed through the DNS, at the next level up in the hierarchy. This means that cloud services also depend on the accuracy and availability of the name servers at higher levels of the DNS hierarchy—each step in the iterative resolution process, including the TLD name servers, as well as the root servers. If the DNS behind a cloud service isn’t working, you probably won’t be able to reach the cloud service. In today’s cloud-dependent world, that’s just one more reason why an ongoing commitment to preserving the security, stability and resiliency of the DNS is critical.

Final Thoughts

The ongoing availability and accuracy of the DNS at all levels of the hierarchy, under various workloads and attacks, is essential to the functioning of cloud-computing platforms. The higher up the DNS hierarchy, the more important resiliency becomes, because a wider range of names and services depend on it. In this sense, the DNS, one of the earliest and most successful distributed systems, may be considered today an essential function as a service: something that cloud platforms and applications all depend on.

By Dr. Burt Kaliski Jr., Senior VP and Chief Technology Officer at Verisign

He leads Verisign’s long-term research program. Through the program’s innovation initiatives, the CTO organization, in collaboration with business and technology leaders across the company, explores emerging technologies, assesses their impact on the company’s business, prototypes and evaluates new concepts, and recommends new strategies and solutions. Burt is also responsible for the company’s industry standards engagements, university collaborations and technical community programs.

Visit Page

Filed Under


DNS is useful but not sufficient for cloud computing Karl Auerbach  –  Jul 29, 2020 3:15 AM

I wrote a note about naming issues in cloud computing way back in 2010 from some meetings at SRI on cloud computing.

On Entity Associations In A Cloud Network

The basic point is that because cloud entities can move, split, rejoin, and become disconnected from one another or have slow links between the sibling pieces DNS names by themselves can not create an adequate or satisfying mapping.

Rather, something richer is needed.

That does not mean that DNS is not useful: That richer name/address can be encoded into DNS labels and resource records so that proven and reliable DNS machinery can be used to look up that information.

(In addition I suggested that we avoid using human-recognizable strings as DNS labels for this, that, instead we avoid trademark and similar issues by using numbers, such as GUIDs.)

Comment Title:

  Notify me of follow-up comments

We encourage you to post comments and engage in discussions that advance this post through relevant opinion, anecdotes, links and data. If you see a comment that you believe is irrelevant or inappropriate, you can report it using the link at the end of each comment. Views expressed in the comments do not represent those of CircleID. For more information on our comment policy, see Codes of Conduct.

CircleID Newsletter The Weekly Wrap

More and more professionals are choosing to publish critical posts on CircleID from all corners of the Internet industry. If you find it hard to keep up daily, consider subscribing to our weekly digest. We will provide you a convenient summary report once a week sent directly to your inbox. It's a quick and easy read.

I make a point of reading CircleID. There is no getting around the utility of knowing what thoughtful people are thinking and saying about our industry.

Co-designer of the TCP/IP Protocols & the Architecture of the Internet



New TLDs

Sponsored byRadix

Threat Intelligence

Sponsored byWhoisXML API

Brand Protection

Sponsored byCSC

IPv4 Markets

Sponsored byIPv4.Global


Sponsored byVerisign

Domain Names

Sponsored byVerisign


Sponsored byDNIB.com