Skip to content

DNS Structure

Arda’s Platform maintains a three-level DNS hierarchy to publish public URLs for all deployed capabilities.

DNS Zone Delegation Structure
GoDaddy (global)
arda.cards domain
└── Platform Root Account (Route 53)
Capability zones: io.arda.cards, app.arda.cards, api.arda.cards, auth.arda.cards
NS records → each Infrastructure zone
└── Infrastructure (Route 53 per Infrastructure)
<infrastructure>.io.arda.cards
<infrastructure>.app.arda.cards
<infrastructure>.api.arda.cards
<infrastructure>.auth.arda.cards
└── Purpose targets (API Gateway custom domains)
<purpose>.<infrastructure>.<capability>.arda.cards

GoDaddy hosts the root arda.cards domain and delegates to the Platform Root account’s name servers.

The Platform Root AWS account hosts Route 53 zones for each capability subdomain:

  • io.arda.cards — current primary API domain
  • app.arda.cards — end-user web applications
  • api.arda.cards — future primary API domain (migration from io.arda.cards is pending)
  • auth.arda.cards — OAuth2 authorization endpoints

Each zone holds NS records that delegate infrastructure-specific subdomains to the corresponding Infrastructure zones.

Each Infrastructure creates Route 53 zones under each capability subdomain:

  • <infrastructure>.app.arda.cards
  • <infrastructure>.io.arda.cards
  • <infrastructure>.api.arda.cards
  • <infrastructure>.auth.arda.cards

Example: alpha002.api.arda.cards

Each Purpose (Partition) within an Infrastructure creates API Gateway custom domains as the final DNS targets:

  • <purpose>.<infrastructure>.<capability>.arda.cards

Example: dev.alpha002.api.arda.cards

Stable names are provided for the standard production release, using the live prefix:

  • live.app.arda.cards
  • live.io.arda.cards
  • live.api.arda.cards
  • live.auth.arda.cards

These canonical names alias to the active prod purpose without encoding Infrastructure-specific identifiers.