Pull Zone origins and hostnames

Understand how Pull Zones connect to origins, issue hostnames, and route traffic across tiers.

Origin types

• Origin URL: point to any HTTPS origin, optionally set a custom host header, and (for admins) tune connect/read timeouts and enable health checks with a custom path.
• Storage Zone: select an existing Storage Zone or create one inline by naming it and choosing a region. This removes public-internet hops and keeps cache hit ratios high.

Naming and DNS

• Zone names must be 4–63 lowercase characters, numbers, and hyphens. Each zone gets an issued name.cdn.gd hostname automatically.
• Custom hostnames are DNS-validated. Add as many as you need; we handle certificates for each hostname with SSL on by default. You can disable SSL per hostname if you need to stage routing changes.

Routing tiers

• standard: default for most workloads.
• volume: built for sustained high traffic or many mapped hostnames.
• Tiers can be changed later from the Routing section without redeploying the origin.

Health and resilience

• Use health checks (admin-only) to probe an origin path and fail fast if upstream is unhealthy.
• Prefer HTTPS origins with valid certificates; set the host header explicitly when your origin expects a specific domain.

Best practices

• Map origins and hostnames deliberately: keep a one-zone-per-application boundary to isolate cache and security settings.
• When fronting a Storage Zone, prefer the Storage origin type instead of the public endpoint to keep requests on the private edge path.