{
  "id": 9447809,
  "title": "Customer Domain Verification: Scheduled Polling and Triggered Rechecks for Tenant Onboarding",
  "url": "https://urgent.news/2026/09/24/customer-domain-verification-scheduled-polling-and-triggered-rechecks",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-09-24T00:15:52.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/valerianblack3895/customer-domain-verification-scheduled-polling-and-triggered-rechecks-for-tenant-onboarding-6ig"
  },
  "original_language": "en",
  "account": "Fintech tenants receive a subdomain from the platform, which is activated through the platform's DNS change. For customer-owned hostnames, the platform conducts scheduled verification in the background and offers a customer-triggered recheck as an additional control. However, a button alone is insufficient to confirm that a DNS change has reached the resolver performing the check.\n\nThe platform uses the DNS ownership boundary to determine the default verification method. A customer-owned zone undergoes scheduled checks, supplemented by a rate-limited recheck. The platform provides separate states like awaiting DNS, verified, and ready to serve, along with the last observed result and check time. It never treats a failed lookup as a permanent rejection, as the customer may still be editing the zone.\n\nThe platform recommends controlling ownership first, with customer-triggered rechecks used only when necessary. The feedback latency is a secondary criterion. While a customer may have published the correct record, a resolver might still be returning an earlier absence. A recheck reports what this verifier observed, not a guarantee of global propagation.\n\nThe verification worker maintains a small state machine, persisting the hostname, tenant ID, challenge, attempt count, next check time, and last observation. A customer-initiated recheck moves an eligible record forward in the queue, calling the same verifier. This ensures that both scheduled jobs and manual rechecks adhere to the same verification rules and avoid disagreements.\n\nIn summary, the verification process prioritizes DNS ownership, uses scheduled checks with customer-triggered rechecks as an optional control, and maintains transparency through distinct states and clear status updates.",
  "summary": "Give each fintech tenant a platform-owned subdomain first, and activate it from the platform's own DNS change. For a customer-owned hostname, run scheduled verification in the background and offer a customer-triggered recheck as an extra control. A button alone cannot establish that a DNS change has reached the resolver doing the check. Short answer: use the DNS ownership boundary to choose the…",
  "key_points": [
    "Fintech tenants receive subdomains activated via DNS change",
    "Platform conducts scheduled verification for customer-owned hostnames",
    "Customer-triggered rechecks supplement scheduled checks"
  ],
  "editors_take": "The platform's verification process for customer domains prioritizes DNS ownership and adds a layer of control with customer-triggered rechecks, while maintaining transparency through clear status updates and distinct states.",
  "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."
}