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

References

  1. We generally advise that email addresses associated with our domain names, such as in Whois records and logins to vendor consoles, be at domain names under our direct control, even if they ultimately forward to another destination.
  2. This preference remains intact even in the aftermath of the very visible, professionally embarrassing Government of Ontario nameserver hijacking that happened on my watch in 2014, the one I described in the "It could have been worse" sidebar in the preface to this book. That said, the Government of Ontario now employs registry locks on their key domains.
  3. DNS Security: In-depth vulnerability analysis and mitigation solutions by Anestis Karasaridis.
  1. Like when Eugene Kashpureff hijacked the Network Solutions internic website in 1997: http://www.theatlantic.com/technology/archive/2011/02/when-the-internet-nearly-fractured-and-how...