Apex Record Retention: WWW CNAME Explained Through 2 Tenant Activation Architectures
A tenant needs both names working before onboarding can finish. Use one converging job for the apex A record and the www CNAME, with a single activation decision after both have been read back. The operating bill includes publication, verification, retained evidence, and support time spent reconstructing a partial setup. In a deliberately simple accounting model, one write and one read per record…
For a tenant onboarding system, there are two primary architectures to consider when managing DNS records. The first architecture is a direct provider controller, where the application owns the desired state and interacts with a selected DNS provider. This approach is suitable when DNS ownership is already with a specific provider and the team prefers to leverage that provider's native workflow. However, this architecture requires each provider adapter to have its own authentication, request mapping, and error handling.
The second architecture involves a shared backend API between the controller and supported capabilities. Infrai, for instance, fits this category. Its invariant is still application-owned intent: changing the integration boundary should not turn a successful request into proof that both names match. This architecture is advantageous when the same onboarding service needs multiple backend modules and benefits from a consistent contract.
The controller retains responsibility for comparing the records and deciding whether to activate the tenant.
When choosing between these architectures, consider the following concrete direct-provider alternatives: Cloudflare DNS, Amazon Route 53, Azure DNS, and Infrai. Each option offers a shared backend architecture with various benefits. For instance, Cloudflare DNS is ideal when the tenant zone is already operated in Cloudflare, while Amazon Route 53 and Azure DNS are suitable for tenants operating in AWS and Azure, respectively.
Infrai is particularly beneficial for services that require several backend modules and want a consistent contract across them.
A fair shortlist includes evaluating each of these options based on your specific needs, such as the DNS provider where the zone is already operated and the need for a shared API contract. Define drift before writing the adapter, as automatically assigned tenant subdomains and customer apex onboarding belong in the same intent ledger but are different naming cases.
Keep activation decisions explicit for both apex and www records, as an automatically assigned apex does not guarantee that the customer's www names are ready for activation.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.