Chapter 4. Managing DNS in a DevOps Culture
DNS can be an important element when managing systems within a DevOps culture, as outlined in this chapter.
However, before this can be reliably implemented, your DNS estate should be managed in an appropriate way to allow the amount of flexibility and dynamic change that will be required.
Traditional DNS Management
Traditionally, DNS was seen as being fairly static, with changes being done only occasionally. DNS changes were done by manually editing a text file on a server, for those running their own DNS servers, or more commonly by submitting a request to the company that managed the DNS records. This change would then take time to propagate through the internet, depending on the TTL set for the record.
This approach was acceptable in a traditional environment of relatively static resources where change was to be kept to a minimum.
However, when implementing a DevOps approach, it is necessary that DNS management is approached in a much more dynamic manner, accepting that change is not only inevitable but an essential element in managing a DNS-driven DevOps implementation.
This includes a change in mindset toward DNS changes.
Remove the Fear of DNS Changes
DNS carries with it an extremely high level of risk. After all, if a mistake is made, it can wipe out connectivity to your site for an extended period, especially in the world where TTL values were typically set to 24 hours.
When combined with the traditionally quite complex or ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access