Book Image

Managing Mission - Critical Domains and DNS

By : Mark E.Jeftovic
Book Image

Managing Mission - Critical Domains and DNS

By: Mark E.Jeftovic

Overview of this book

Managing your organization's naming architecture and mitigating risks within complex naming environments is very important. This book will go beyond looking at “how to run a name server” or “how to DNSSEC sign a domain”, Managing Mission Critical Domains & DNS looks across the entire spectrum of naming; from external factors that exert influence on your domains to all the internal factors to consider when operating your DNS. The readers are taken on a comprehensive guided tour through the world of naming: from understanding the role of registrars and how they interact with registries, to what exactly is it that ICANN does anyway? Once the prerequisite knowledge of the domain name ecosystem is acquired, the readers are taken through all aspects of DNS operations. Whether your organization operates its own nameservers or utilizes an outsourced vendor, or both, we examine the complex web of interlocking factors that must be taken into account but are too frequently overlooked. By the end of this book, our readers will have an end to end to understanding of all the aspects covered in DNS name servers.
Table of Contents (17 chapters)
7
Types and Uses of Common Resource Records

Introducing resolvers

The two main variants of nameservers represent both sides of a DNS lookup process: a query (resolver) and a response (authoritative nameserver).

Remember my original "elevator pitch" about how DNS works:

"Every time you send an email, visit a web page, type or receive an instant message, text, or SMS, place a VoIP call (or Skype), or anything else involving the internet, it cannot happen until a bunch of computers around the internet have a conversation about it: Where does this email need to be delivered to? What server is holding the file that this web browser is asking for? Where is the VoIP gateway that needs to route this call?"

The computers, or applications or daemons that are actually asking these questions are the resolvers.

Your clients are more often applications such as web browsers or email clients, than they are people. Those...