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

Who this book is for

Your time will be well spent in reading this book if the following is true:

  • You are responsible for at least one mission-critical domain that must be online 24x7x365, or you are part of a team that manages large groups of domains, in the hundreds, thousands, or above, on behalf of your company or on behalf of your downstream users.

  • Your responsibilities include maintaining your organization's core DNS or DNS for its downstream users or clients, even if you accomplish these tasks by outsourcing DNS management to external providers. (This can include sysadmins, webmasters, IT consultants, and developers.)

  • You work for a technology company, or you are in tech, your core competency is something other than domains and DNS, but you or your company relies on functioning domains to carry on your business (which is almost everybody these days).

Here's a basic acid test: If your company's or perhaps one of your client's key domain names went offline for any reason, would you be one of the people who will be paged after hours, woken up in the middle of the night, grilled, yelled at, or possibly fired afterward? If the answer is "yes" or "maybe", this book is for you.