{
  "id": 21137818,
  "title": "Customer Domain Support in Go: Why I Chose Apex Record Ownership",
  "url": "https://urgent.news/2026/11/21/customer-domain-support-in-go-why-i-chose-apex-record-ownership",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-21T23:37:51.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/liraelvex6403/customer-domain-support-in-go-why-i-chose-apex-record-ownership-56c2"
  },
  "original_language": "en",
  "account": "Apex A records and www CNAMEs are essential components in customer domain support. A CNAME cannot be used at the apex of a domain, so an A record pointing to a documented address is recommended, along with a CNAME for www. This approach ensures portability during onboarding and avoids coupling the address to support replies. Once the address is published in the customer's zone, the platform can update its intended value independently. It is crucial to budget migration work based on the number of customer zones still publishing the old address, distinguishing between zones that can be modified by the platform and those requiring customer action. The portal and mail readiness should have separate explanations, with apex A record and www CNAME addressing the portal's entry points. The mail checklist should retain intended authentication records and their publication evidence, with DMARC reviewed separately. There is no universal mail record value to use in the onboarding flow, so the migration should have a narrow repair scope without becoming a permission to overwrite unrelated mail records. A stable operation identity should be retained across retry attempts, and the intended change should be persisted independently of any idempotency window. Response errors should provide sufficient context to identify the change, with an internal activation SLO measuring portal and mail acceptance separately. Capacity planning should consider affected zones, observations per zone, and the permitted retry budget. Customer-controlled updates will always require coordination, even when API capacity is sufficient.",
  "summary": "Retries belong behind a reconciliation check. For property managers publishing customer domains and mail authentication records, I would choose a documented apex A record and a www CNAME, accepting the obligation to coordinate future address changes rather than treating a successful write as proof that the customer's zone matches intent. TL;DR: standard DNS forbids an apex CNAME; an A record is…",
  "key_points": [
    "Apex A records and www CNAMEs recommended for customer domain support",
    "Separate explanations for portal and mail readiness during onboarding",
    "Capacity planning considers affected zones and retry budget"
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}