The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →To connect a custom domain to a deployed web app, add the domain in your hosting project, enter the DNS records that host specifies at the service managing your domain’s DNS, then wait for verification and confirm HTTPS works. The exact records depend on your host and whether you’re using a root domain such as example.com or a subdomain such as www.example.com.
Before you change DNS
Three services may be involved: your registrar, where you registered the domain; your DNS provider, which manages its active DNS records; and your app host, which serves the web app. They can be different companies. Make DNS changes wherever the domain’s active DNS is managed, not automatically at the registrar or app host.
- Choose the hostname you want visitors to use: the root (apex) domain, such as
example.com, or a subdomain, such aswww.example.comorapp.example.com. - Sign in to the hosting project that serves the deployed app and find its custom-domain or domain settings.
- Keep the host’s instructions for your specific project available. Generic examples are not a substitute for the DNS values shown in your project.
Connect the domain in the right order
- Associate the hostname with the app. In your host’s project settings, add the exact domain or subdomain you intend to use. Some hosts require ownership verification or a specific setup flow before DNS changes. Follow the host’s order rather than adding records first.
- Read the project-specific DNS instructions. Note the record type, name or host, and value or target. Root domains and subdomains can need different record types. Do not copy a value from another provider’s tutorial unless your project specifically requests it.
- Edit DNS at the active DNS provider. Create or update the records exactly as instructed. Check the record name as well as its value: DNS dashboards may represent the root domain with a blank name or an
@, depending on the provider. - Return to the hosting project and verify. Use its status or verification control after saving DNS. The platform may need time to see the new records.
- Check HTTPS and the app itself. Confirm the host reports the domain and certificate as ready, then visit the exact hostname using
https://. Check that the expected app loads, not just that a DNS lookup returns a record.
How setup differs by platform
The host’s current project instructions take precedence over generic DNS patterns. These official guides describe the important differences:
| Platform | Association and DNS setup | Verification, HTTPS, and timing |
|---|---|---|
| Vercel | Add the domain to the project, inspect its required DNS configuration, and enter those values with your DNS provider. Project-specific values can differ from general examples. | Vercel says it automatically provisions an SSL certificate after DNS verification. Its guide says propagation can take a few minutes; this is platform guidance, not a guarantee. Vercel’s domain guide was last updated March 12, 2026. |
| Cloudflare Pages | For an apex domain, the domain must be a Cloudflare zone and its nameservers must point to Cloudflare. Complete the Pages custom-domain association flow; a CNAME by itself is not sufficient. | Cloudflare warns that adding the CNAME without first associating the domain in Pages can result in a 522 error. See Cloudflare Pages custom domains (last updated April 21, 2026). |
| Netlify | Add the domain under the site’s Domain management area, then choose Netlify DNS or an external DNS provider. For an external provider, follow the site’s pending-verification instructions rather than assuming a generic record. | Netlify says DNS changes may take up to 48 hours to take full effect and suggests using dig to check propagation. That is provider guidance, not a universal DNS deadline. See Netlify’s external DNS instructions and Netlify’s troubleshooting tips. |
| GitHub Pages | Verify ownership before adding the domain to the repository, then add it to Pages before configuring DNS. GitHub documents A and AAAA records for an apex domain (or ALIAS/ANAME where supported) and a CNAME for a subdomain targeting the account or organization’s github.io address. |
GitHub strongly advises against wildcard DNS records because of takeover risk. Follow GitHub’s verification instructions and custom-domain DNS guidance. |
Root domain or subdomain: why it matters
A root domain (also called an apex domain) is the bare name, such as example.com. A subdomain adds a label, such as www.example.com or app.example.com. Hosts may require different record types for these two cases. For example, GitHub Pages documents A/AAAA records (or ALIAS/ANAME where supported) for an apex and a CNAME for a subdomain. Other hosts may give different values or require a different arrangement.
Free tools Windows power users keep installed
One-click scans. No signup required.
#1 Best Overall
Some platforms also impose a DNS-provider requirement. Cloudflare Pages requires Cloudflare nameservers for an apex domain; this is not the same as adding or editing a record. Other setups may allow you to keep an external DNS provider. Before changing nameservers, check the host’s instructions and understand that nameserver delegation changes which service manages the domain’s DNS.
Verify DNS and troubleshoot a domain that is not working
If the host still shows the domain as pending, work through these checks in order:
- Confirm the DNS provider. Make sure you edited records at the provider currently authoritative for the domain. The registrar and DNS provider may be different.
- Compare every field with the project instructions. Check the record type, host/name, and target/value, as well as whether the instruction applies to the apex or a subdomain. Remove conflicting or obsolete records only when you know they are not needed for another service.
- Check the host’s required setup sequence. Confirm the hostname is attached to the correct project or account and that any ownership verification is complete. A record that points at a service may not work if the service has not associated the hostname.
- Allow for propagation, then check again. Re-run the platform’s verification. If you use a terminal,
digcan show the DNS answer visible to your resolver; it does not by itself confirm the host has associated the domain or issued a certificate. - Inspect HTTPS and the response. Check the host’s certificate or domain status, then load the intended hostname over HTTPS. A resolved DNS record and a working, secure app are separate checks.
Protect the domain from takeover
Only point a hostname to a service after you have associated it with the right account or project and completed ownership verification where the host supports it. GitHub recommends verifying a custom domain before adding it to a repository to improve security and avoid takeover attacks. It also warns against wildcard DNS records, which can expose unclaimed subdomains to takeover.
Quick Recap
Best Value
Rank #4
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
