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

For DNS providers

All of this applies to DNS providers as well: registrars, web hosts, ISPs, managed DNS operators, and so on. What changes is the scale one is operating at and the mechanics of effecting step 3, that of adjusting your DNS setup in response to outages or degraded conditions.

Here, we refer back to our Chapter 12, Nameserver Considerations, when it comes to selecting address space for numbering your nameservers. Ideally, you control its address space so that you can easily move traffic around, using routing announcements if you have to.

This is what I was alluding to Chapter 12, Nameserver Considerations, about moving traffic into DDoS scrubbing centers during an attack using BGP.

One model we used for awhile with great success was a combined anycast/unicast architecture, where under normal course operations, a particular nameserver entity was an anycast-deployed...