DNS Setup for PWA

DNS setup for PWA is what points a purchased domain at the server running the PWA — without the right records the domain won't load the page or get HTTPS at all. Here's which record type to use (A or CNAME), why buyers often proxy through Cloudflare, and how to deploy a new domain onto a funnel fast, without downtime.

A record or CNAME: which to use

An A record points the domain straight at a server's IP address and works well when the funnel has a fixed, dedicated IP. A CNAME points at another domain name — a platform's technical subdomain hosting the PWA, for instance — and is more convenient when the IP can change, since you're not manually updating the record every time the server changes. Most setups on a ready-made PWA platform use a CNAME to the platform's technical address, while an A record fits when you're running your own infrastructure.

Why proxy through Cloudflare

Proxying hides the server's real IP from direct scanning and adds a layer of protection against some bots and DDoS traffic before it ever reaches your infrastructure. It also makes it easy to switch a domain between servers quickly, or pull a zone offline temporarily during issues, without touching records at the registrar. The trade-off is a bit of extra latency at the proxy layer, and the SSL mode needs to match the server's certificate — Full or Full Strict, not Flexible.

Common mistakes in record setup

The most common one: leaving the old A record pointed at a previous IP after switching servers or platforms, so the domain quietly leads nowhere until it's updated. The second: TTL set too high, so a record change takes hours to propagate worldwide right when a domain urgently needs to relaunch after a ban. The third: Cloudflare proxying turned on with SSL mode set to Flexible, which breaks the HTTPS connection to the PWA and blocks installation.

How to speed up deploying a new domain

Lower the TTL on records ahead of a planned domain swap — changes then propagate faster once the swap actually happens. Keep a template of the records (type, name, value, TTL) on hand instead of rebuilding them from scratch every time a new domain gets connected to the same funnel. Check propagation with a dedicated DNS-checking service rather than trusting your own browser — local DNS cache can show the updated result before the rest of the audience sees it.

How APEX simplifies domain connection

In APEX, connecting a custom domain and issuing the HTTPS certificate is automated: once the right DNS records are added at the registrar, the platform verifies them and issues the certificate without manual work at a certificate authority. One-click rotation means a new domain, once a previous one gets banned, connects and gets HTTPS without repeating the whole manual setup chain — especially valuable when domains need swapping often.

FAQ

What happens if the old DNS record stays after a server switch?
The domain keeps pointing at the old address, so visitors either hit someone else's server, an empty one, or an error — access to the PWA only comes back once the record is updated and has propagated.
Is proxying through Cloudflare required for a PWA?
No, it's optional, but many buyers use it to hide the real server IP and block some scanners — the key is setting the right SSL mode so it doesn't break HTTPS to the PWA.
How long does a new DNS record take to propagate?
Usually anywhere from a few minutes to a couple of hours depending on TTL and provider — lowering TTL ahead of a planned domain swap speeds this up.
Does DNS need manual setup on every domain rotation in APEX?
The platform handles the bulk of it — issuing and updating the HTTPS certificate — once the domain is connected, which speeds up rotation considerably compared to a fully manual setup.
Build your PWA in APEX in minutes

Cloaking, anti-bot, push, split tests and your own domains — in one service.

Get started free

Read also