Urgent.News

What's breaking now, across hundreds of outlets.

Tech

Customer Domain Support in Go: Why I Chose Apex Record Ownership

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…

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.

Rewritten by urgent.news; may contain errors — check the original.

Read the original at dev.to →

Report a problem with this story

More in Tech

German e-invoicing for developers: XRechnung and ZUGFeRD via REST API and MCP

From 2027, many German businesses have to send structured e-invoices to other businesses, and from 2028 almost all of them. Receiving them has been mandatory since 1 January 2025.

  • German businesses must send e-invoices by 2028, starting 2027 for high-revenue firms
  • XRechnung is pure XML (UBL or CII syntax) format
  • ZUGFeRD combines PDF/A-3 with embedded XML

Is This Height Comparison Up to Scale? How to Draw One Correctly in JavaScript and SVG

"I've always wondered what a height different between a 4'10 person and a 5'7 person would look like … I found this image but idk if it's up to scale or not." That question, posted to r/heightcomparison, is the whole genre in one sentence.

  • Figures' feet should be on the same horizontal line (single ground line)
  • Scale must start at zero, consistent pixels per centimeter throughout
  • Incorrect scaling introduces bias, distorts visual representation

ILLA Builder's 92 Fingerprints Mark a Low-Code Control Plane With Data Connections

ILLA Builder's 92 Fingerprints Mark a Low-Code Control Plane With Data Connections ILLA Builder is designed to assemble internal tools from visual components, data sources, and actions. That makes the builder more consequential than a static dashboard.

  • ILLA Builder identified via 92 distinct fingerprints
  • Control plane connects to databases, APIs, MongoDB, Redis, Hugging Face
  • November 22, 2026: ZoomEye SDK finds 92 app name matches, 109 body content matches

More from Saturday 21 November →