Skip to main content
DNS Records Done Right — Proper naming and documentation prevents authentication failures and confusion. Check Your Setup →

What are the best practices for naming and documentation?

Record naming:

  • Clear purpose in subdomain names (mail., tracking., selector1._domainkey.)
  • Consistent conventions across domains
  • Avoid cryptic abbreviations

Documentation content:

  • What each record does
  • Who is responsible for it
  • When it was created/modified
  • Why it exists (context)
  • Dependencies (what breaks if removed)

Format:

  • Table or structured document
  • Linked to any related service documentation
  • Accessible to all relevant team members

Without documentation, DNS becomes tribal knowledge that is lost when people leave or forget.

Clear labels on every document in the registry. Anyone should understand each entry's purpose.

Need personalized help?

Build a DNS naming + docs system that scales. Open an AI assistant with your question pre-loaded — just add your details and send.