{
  "id": 15246913,
  "title": "Fintech Apex Domain Support in Node.js: 3 Customer Record Cutover Rules",
  "url": "https://urgent.news/2026/10/17/fintech-apex-domain-support-in-node-js-3-customer-record-cutover-rules",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-17T17:47:42.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/kaelvyn47/fintech-apex-domain-support-in-nodejs-3-customer-record-cutover-rules-4ed8"
  },
  "original_language": "en",
  "account": "The source material outlines best practices for handling customer domain support in fintech onboarding using standard DNS configurations. Key points include:\n\n1. Publish an A record for the apex domain (e.g., example.com) and a CNAME for www.example.com. An A record is preferred over a CNAME at the apex due to DNS limitations.\n\n2. Verify both records before completing the onboarding process. This ensures the customer can access the service at either example.com or www.example.com.\n\n3. The onboarding contract should track three states: the expected apex A record, the expected www CNAME, and the observed verification result. The verification result should include the hostname checked, expected type, normalized answer, observation time, and a bounded status like \"pending\" or \"verified\".\n\n4. Retention of DNS verification data should be balanced. Storing every raw response creates large volumes (e.g., 6 GB for 100,000 attempts with 60 polls each). Instead, store a current result per hostname and transitions between states, along with aggregate metrics to analyze capacity and propagation.\n\n5. The recommended apex support approach is an A record for the apex domain and a CNAME for www. Managed DNS providers offer proprietary apex indirection that is not portable. The instructions focus on a portable contract of apex A plus www CNAME.\n\nIn summary, the key recommendation is to use an A record for the apex domain and a CNAME for www, with verification tracking and retention focused on minimal, meaningful data to support onboarding and troubleshooting without creating unnecessary coupling or storage burdens.",
  "summary": "TL;DR: For a fintech onboarding flow, publish a documented A record for the customer's apex and a CNAME for www , then verify both before onboarding completes. Standard DNS forbids a CNAME at the zone apex, so an A record is the portable choice. The operational price is coupling: when the service address changes, every customer using the apex must update a record in a zone you do not control.…",
  "key_points": [
    "Publish A record for apex domain, CNAME for www",
    "Verify both records before onboarding completion",
    "Track expected apex A, www CNAME, and verification result"
  ],
  "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."
}