Your pages
All guides

Connect your church’s domain

Use a church-owned address when domain setup is available, with instructions for your DNS provider.

Updated October 2, 2026. Domain setup is implemented locally and remains disabled until the operator configures and verifies Cloudflare for SaaS. Do not change DNS while the app says it is not configured.

Choose your address

Use your PewCard address, or connect one church-owned custom subdomain per church account. For example, links.yourchurch.org opens the selected default hub; links.yourchurch.org/youth and /men open the corresponding ministry hubs. These are independent link hubs, not a website builder. Each hub must be published separately. The default hub also remains available at its named path, such as /main.

Apex/root custom domains such as yourchurch.org and yourchurch.co.uk are not supported, even if your DNS host offers flattening or ALIAS. Choose a subdomain: links.yourchurch.org, hub.yourchurch.com, or connect.yourchurch.co.uk. “links” and “.org” are examples, not requirements. One connected subdomain serves all your hubs; each ministry uses a path, not another hostname. Preserve your main website’s root A/AAAA records and any existing www record.

Your Account page shows current subscription pricing. Domain registration is separate. Setup requires confirmed paid or complimentary access; the free trial does not include domain setup. Existing custom-domain pages follow paid coverage and the 30-day public grace period. Suspended/deleting accounts are unavailable immediately. An unpublished page remains unavailable even when its domain is active.

Find the right DNS account

The registrar sells/renews the domain. The authoritative DNS host stores the records used by the internet. They can be different: a domain purchased from GoDaddy can use Cloudflare DNS. Check the domain’s current nameservers in the registrar account, and edit records at the provider those nameservers identify. Ask your church’s website administrator if unsure. You do not need to transfer the domain or change nameservers for ordinary subdomain setup.

Set up in PewCard

  1. Sign in at your usual PewCard address and open Account → Your church’s domain.
  2. Enter the subdomain only: no https://, slash, port or wildcard. International names must use valid punycode; choose a hostname no longer than 233 characters so verification record names fit in DNS. Select the default hub for /, then choose Start domain setup. The saved setup survives leaving the page.
  3. Copy the generated PewCard ownership TXT into your DNS host. Keep it there for ongoing ownership checks.
  4. Choose Check DNS & HTTPS. Once PewCard finds your TXT, it requests the Cloudflare hostname and certificate. This may reveal additional Cloudflare ownership and HTTPS certificate TXT records. Add every record shown; values are unique to your setup and can change during certificate renewal.
  5. Add the traffic CNAME to the exact target shown in the app. Use the chosen subdomain as its name, never @. Do not point directly to the staging workers.dev address or invent A-record IPs.
  6. Check again after propagation. Both Hostname: active and HTTPS: active are required. Then open your domain and each published ministry path in a signed-out browser. Check images and links too.

Starting setup does not publish drafts, start a Stripe charge, or edit DNS automatically. Keep using your existing PewCard addresses until your custom domain works. The editor’s existing share links and generated QR codes continue using those stable PewCard addresses; you can copy the custom address from Account when ready.

What the generated records mean

The app shows full DNS names. Some providers append your zone automatically: for the zone yourchurch.org, enter links instead of links.yourchurch.org, and _pewcard.links instead of _pewcard.links.yourchurch.org. Verify the saved full name to avoid duplicated suffixes. These examples are not working records; copy the actual values from your account.

Purpose Type Example name Value
PewCard ownership TXT _pewcard.links.yourchurch.org Unique token displayed in Account
Cloudflare ownership, if shown TXT _cf-custom-hostname.links.yourchurch.org Provider-generated value displayed in Account
HTTPS validation, if shown TXT _acme-challenge.links.yourchurch.org Each provider-generated value displayed in Account
Subdomain traffic CNAME links.yourchurch.org Operator-configured target displayed in Account

Use the DNS host’s default TTL (or 300 seconds if offered). Enter TXT values without adding extra literal quotation marks. If multiple certificate TXT values share a name, keep all requested values as separate records. Do not replace email SPF/DKIM/DMARC or MX records.

Provider instructions

Use the provider that actually hosts your DNS. Interface wording can change; the official pages linked below are the source for navigation. Complete all generated TXT records as well as the traffic record.

Cloudflare DNS

Select the domain → DNS → Records → Add record. Add TXT records using the generated name/content. For a subdomain, add CNAME, name links, target from PewCard, DNS only (gray cloud), TTL Auto. Keep verification records DNS only if another verification method later supplies a CNAME.

Keep existing website and mail records. See Cloudflare DNS records.

GoDaddy

Open Domain Portfolio → your domain → DNS → Add New Record. Add TXT records with the appropriate relative Name and exact Value. Add a CNAME named links, using the generated target as Value. Save and complete any account verification requested by GoDaddy.

Use your chosen subdomain prefix, never @. CNAME instructions, TXT instructions, which DNS account to use.

Namecheap

Open Domain List → Manage → Advanced DNS → Host Records → Add New Record. This applies when the domain uses Namecheap DNS, not external nameservers. For a subdomain choose CNAME Record, Host links, Value the PewCard target; add TXT records with their relative Host and exact Value. Save each record.

Use CNAME for the subdomain; root ALIAS records are outside PewCard’s supported setup. Host records, CNAME.

Whois.com

In your domain’s management page, open DNS Management / Manage DNS for the active DNS service. Add a CNAME record for links with the displayed destination, then the generated TXT records. Check whether the form appends your domain automatically. If nameservers point elsewhere, edit at that DNS host instead; do not activate or replace nameservers merely to find these controls.

Use the selected subdomain, not a blank root Host Name. DNS management, DNS service navigation.

Squarespace Domains

Open Domains dashboard → your domain → DNS → DNS Settings → Custom Records → Add record. Choose CNAME, Host/Name links, Data the generated target. Add each TXT record with its corresponding name and value. Complete Squarespace’s account verification if prompted.

Leave Squarespace Defaults and root website records in place when adding your subdomain. DNS web-hosting records, pointing a subdomain.

Wix

Open Domains → your domain’s actions → Manage DNS Records. Under CNAME (Aliases) add the subdomain Host Name links and generated Value. Add each TXT under the TXT section; save and confirm changes. Use the selected subdomain, not a blank root Host Name.

When your Wix website was connected by pointing and DNS remains elsewhere, make edits at that external DNS provider. External subdomain, DNS records.

Other providers, including hosting-company DNS

Open the zone’s DNS/Zone Editor, add CNAME for the selected subdomain and all generated TXT records, and save. Verify full names and values. Ask support how to add a CNAME for your chosen subdomain without changing existing website or email records. A registrar’s web forwarding is not this setup.

Pending states and troubleshooting

  • Ownership pending: check the authoritative nameservers, exact _pewcard name/value, accidental duplicated domain suffixes, and extra quotation marks. PewCard deliberately will not provision a hostname on the strength of an old traffic CNAME alone.
  • HTTPS pending: add every generated provider TXT. Tokens may appear a little later; check again. Cloudflare also attempts HTTP certificate validation for non-wildcard names after traffic points to its SaaS target. Certificate TXT behavior.
  • CAA / DNSSEC / certificate errors: review the specific provider message with your DNS administrator. Fix incorrect CAA permissions or broken DNSSEC through the DNS host; do not turn security settings off indiscriminately. Never bypass a browser certificate warning.
  • Propagation: changes may be visible within minutes, but cached positive/negative answers and provider timing can take longer, sometimes 24–48 hours. Do not repeatedly recreate setup. Pending and active setups become eligible for another check on the next hourly run. Maintenance selects at most 50 due hostnames and shares a smaller work budget with other background tasks, so this is not a promise of 50 completed checks per hour. Queued checks can take longer. Manual checks are rate-limited to one every 15 seconds.
  • Previously saved root domain: it cannot serve hubs or show usable DNS setup records. Disconnect it, then connect a supported subdomain. Provider removal remains retryable.
  • Interrupted request: use Reload saved status first. The same setup is reused, including a provider create whose response was lost. Inputs survive visible errors. If removal is pending, retry; do not create a competing setup elsewhere.
  • Active but page unavailable: publish the correct hub; check the default selection, exact ministry slug, and paid/grace status. Active means the provider hostname and certificate passed the last check, not that a draft became public. Requests fail closed after 48 hours without a successful ownership/provider check.
  • Only one address works: only the subdomain you connected serves your hubs. The root domain and other subdomains do not become PewCard addresses. /youth is a path and needs no additional DNS record.
  • Cloudflare error or already-existing hostname: retry later or contact PewCard support. An unrelated existing provider hostname is never silently adopted. Keep the existing church website working while support resolves it.

Change or disconnect

Changing Page at your main address changes / only. Existing named ministry paths still work. Deleting the selected default page queues removal of the hostname; select another default before deleting it. Unpublishing merely makes that page unavailable. Account deletion also queues provider removal, with immediate public visibility blocking.

Before disconnecting, remove or repoint the traffic CNAME at your DNS host. In PewCard expand Disconnect this hostname, acknowledge the effect, and disconnect. Routing stops immediately; keep checking until the saved hostname disappears and provider removal is confirmed. Then remove the PewCard/provider verification records you added, without touching unrelated TXT records. Provider outages leave a visible retryable disconnect state. The ordinary PewCard addresses and content remain subject to normal account access rules. Custom-domain printed links and QR codes will stop working. A later connection gets a fresh ownership token.

Hourly domain processing shares the invocation budget with other background work. The 50-record selection limit is not hourly throughput; checks can be deferred. See capacity and activation requirements. Manual owner checks remain immediate.

An unfinished setup expired

An unverified setup expires after 24 hours and can be started again with a new verification token. Only a verified claim reserves a hostname; an unfinished setup cannot reserve another church’s address. Use the latest TXT record shown in Account. Provider removal and cleanup may need to finish before reconnecting an address that was already registered.

Still need help? Contact support, or ask the person who gave your church access.