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

POOL records (multiple CNAME RRSet)

Multiple CNAME RRSets, which is having multiple CNAMEs for the same name, are not as in-demand as apex aliases, but there are use cases for them. To make matters more confusing, these actually used to work back in the BIND4 days, then optionally worked later under BIND8 (with the allow- multiple-cnames option enabled) and were discontinued as of BIND 9.1.

Now most people will simply point at the "CNAME cannot coexist with other data" rule and leave it at that.

The POOL record would then implement multiple CNAMEs, such as:

us.example.com.IN CNAME us1.provider.example. 
us.example.com. IN CNAME us2.contributed.dom.
us.example.com. IN CNAME www4.example.net.

The nameserver would be responsible for cycling through the available results, just as in the case of a round-robin of A or AAAA records. However, instead of returning all available...