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

What individual domain owners can do

The preceding solutions may be out-of-reach for individuals or small organizations, or even big ones whose core competency lies elsewhere.

Thus, when seeking to maximize uptime on your own domains, it's all about redundancy.

When the DNS specification and associated RFCs were first published, redundancy was cultivated by simply virtue of having "multiple" (that is, two) nameservers, on disparate networks. To wit, nameservers should be as quoted.

"both topologically and geographically dispersed locations on the Internet, to minimise the likelihood of a single failure disabling all of them."

This is no longer enough. In the modern, commercialized internet of today, each DNS provider or DNS operator must be treated as a logical Single-Point-of-Failure unto itself.

The complexity...