DNS Management for a Multi-Service Software Environment
Industry
B2B Software
Service
DNS Management
The Situation
A B2B software company relied on a growing stack of connected services — a hosted website, an email provider, several SaaS tools requiring domain verification, and subdomains supporting staging and customer-facing integrations. Different engineers added DNS records incrementally over time, with no single documented source of truth.
What Was at Stake
This is a common, specific failure mode: servers remain healthy and code deploys cleanly, yet the site still goes down because a TTL was misconfigured, a verification TXT record was overwritten, or someone unaware it was live edited an MX record. DNS is infrastructure that stays invisible until it breaks something else.
The Approach
Every A, AAAA, CNAME, MX, and TXT record cataloged and mapped to the specific service it supports
Verification records for third-party tools clearly labeled and separated from core website and email records
TTL values reviewed and standardized to reduce propagation risk during planned changes
A lightweight change-control process introduced for production DNS edits, including a documented rollback record
Outcome
DNS changes stopped being a source of uncertainty. The team could evaluate a proposed change against a documented dependency map rather than relying on institutional memory.
IT Decision-Maker Perspective
DNS warrants the same change discipline as production code — documentation, review, and a rollback plan — since its failure modes are often more disruptive and harder to diagnose than a typical application bug.