6 min read PUBLISHED: 2026-10-15

Understanding DNS, Domains, Subdomains, and Static Hosting Separation

Why configuring a URL in application code is distinct from DNS resolution, TLS provisioning, and multi-subdomain deployment architecture.

DNS Domains Cloudflare Pages Architecture

Separating Code Configuration from Infrastructure Reality

One of the most common misconceptions when structuring a multi-site developer ecosystem—such as pairing an identity hub at satyabuilds.com with specialized portals like projects.satyabuilds.com or blogs.satyabuilds.com—is treating a URL string in a configuration file as if it automatically provisions routing.

In practice, reliable deployment requires keeping three layers strictly distinct:

  1. Application Configuration Layer: Centralizing canonical URLs and external destination references in a single source of truth (src/config/site.ts) so templates never contain hardcoded strings.
  2. DNS Resolution Layer: Publishing explicit authoritative records (A, AAAA, or CNAME) at the DNS provider that map each hostname or subdomain to a specific edge target.
  3. Host Binding & TLS Layer: Registering the custom domain inside the hosting platform (such as Cloudflare Pages) so the edge proxy recognizes the incoming Host header and serves a valid TLS certificate.

How Subdomain Routing Actually Resolves

When a browser requests projects.satyabuilds.com, it does not inspect the main portfolio repository unless DNS explicitly tells it to.

Browser Request (projects.satyabuilds.com)
   │
   ├─► 1. Recursive DNS Resolver queries Authoritative Nameserver
   │      Returns CNAME -> <project-portal>.pages.dev
   │
   ├─► 2. TLS Handshake & SNI Negotiation at Edge Node
   │      Verifies certificate matching projects.satyabuilds.com
   │
   └─► 3. Edge Host Header Dispatch
          Routes request to the specific build artifact bound to that subdomain
          Because each subdomain can point to an entirely independent repository and build pipeline, an engineering portfolio can start as a self-contained monolith (serving /projects and /writing locally) and later split heavy interactive apps onto dedicated subdomains without breaking internal architecture.
Defensive Link Hygiene in Static Sites

Until a subdomain's DNS record is live and its target deployment is verified, linking to it as an active navigation item creates dead ends for visitors. A resilient frontend configuration tracks both the intended URL and a verification flag:
TypeScript

export interface ExternalPortal {
  label: string;
  url: string;
  verifiedLive: boolean;
}

When verifiedLive is false, the interface can transparently communicate the planned domain architecture without rendering broken hyperlinks.
← Back to Writing Index