Chapter 2. DNS Primer
In many ways, DNS is the public face of the internet. It allows friendly names such as google.com to be used instead of unfriendly IP addresses.
Although it is a fundamental element to successful operation of the internet as we know it, for many developers the DNS system is a black box, something they rely on but assume will always “just work.”
In some ways, DNS has been a victim of its own reliability. In general, with simple systems it is possible to just ignore DNS and it will just work. As systems become more complex, however, DNS is another tool that can be used both to mitigate problems and to optimize performance and delivery of systems.
As discussed in Chapter 1, this is another example of the DevOps culture blurring the distinction between development and operations, requiring developers to think about elements that were previously entirely the domain of operations.
How Does DNS Work?
It is surprising how many developers have only a very limited or even no understanding of how the DNS process actually works. So it may be useful to give a quick, high-level overview of the process that is followed when a DNS resolution request is made.
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access