Domains

DNS records reference

Copy-paste DNS records for connecting a custom domain to PageFork.

When you connect a custom domain, PageFork shows the exact records to add — use those. This page is a reference for planning ahead or when your registrar’s UI doesn’t line up with the PageFork flow.

The values in the PageFork domain sheet are authoritative. If they differ from this page, use what the app shows you (especially the redirect IP in Case D).

The target host

Every CNAME record for PageFork points at the same host:

sites.pagefork.ai

That’s the only valid CNAME target. PageFork’s edge handles routing, caching, and SSL for every domain that CNAMEs here.

Case A — Subdomain (not www)

One CNAME on the subdomain:

TypeNameTargetTTL
CNAME(e.g. launch, go, app)sites.pagefork.aiAuto / 300

The simplest setup and the one we recommend for campaign pages or sub-brands.

Case B — www only (no apex)

One CNAME on www:

TypeNameTargetTTL
CNAMEwwwsites.pagefork.aiAuto / 300

Visitors who type the bare apex (yourbrand.com) will hit whatever the apex currently serves — often a registrar parking page or another app. If you want both to work, see Case C or Case D.

Case C — Apex with ALIAS / CNAME flattening

Available on Cloudflare, DNSimple, Netlify DNS, Route 53, and a few registrars. One record at the apex does the whole job:

TypeNameTargetTTL
ALIAS or CNAME (flattened)@ (or blank)sites.pagefork.aiAuto / 300

The cleanest option when your provider supports it.

Case D — www + apex, without ALIAS / flattening

The fallback for registrars that only support classic A / CNAME. Two records, both required:

TypeNameTargetTTL
CNAMEwwwsites.pagefork.aiAuto / 300
A@(redirect IP shown in the PageFork app)Auto / 300

Important details:

  • The A record doesn’t serve your site. It points at PageFork’s tiny redirect service, which 301-redirects the apex to www. Your site is served from the www CNAME.
  • The A record is only valid paired with the www CNAME. An A record without a matching www CNAME won’t verify.

There is no A record that points directly at PageFork’s site edge. CNAME to sites.pagefork.ai is the only way for a record to serve your site.

What TTL should I use?

Any low value works — 300 seconds (5 minutes) or your provider’s Auto setting is fine. Avoid 24h+ TTLs while you’re setting things up; long TTLs make DNS issues painful to debug.

Verifying the records

In PageFork, your domain moves through these states:

  • Pending — records haven’t been seen yet.
  • Validating — records found; SSL is being provisioned.
  • Active — live over HTTPS.
  • Failed — the error message says what’s wrong.

Click Refresh status any time to force a recheck.

Common gotchas

  • Proxied records (Cloudflare’s orange cloud, other CDNs). Must be off for every PageFork record — the CNAME, the apex redirect A, the ALIAS. See Cloudflare and proxies.

  • Existing A records at @ from a previous host. Remove them before adding PageFork’s records; stale A records shadow the redirect setup.

  • AAAA records at @ or www pointing elsewhere. Remove them, or they’ll be preferred on IPv6 and skip PageFork entirely.

  • Wildcard records (* → something). You don’t need to remove or change these. Two reasons:

    • In standard DNS, * does not match the apex (@). A * A 1.2.3.4 record answers for anything.yourbrand.com but never for yourbrand.com itself, so it doesn’t conflict with the Case D apex A record you add for the PageFork redirect.
    • Specific records always win over * anyway. Your www CNAME to sites.pagefork.ai takes precedence over a * CNAME pointing somewhere else.

    Just know that any subdomain you haven’t explicitly configured will still fall through to the wildcard’s target.

  • TXT records for email (SPF, DKIM, DMARC). Leave them alone — PageFork doesn’t touch them.

Next

Previous Apex vs www Next SSL certificates