Finishing a custom domain setup comes down to three moves: add the domain inside your platform dashboard, update your DNS records at the registrar (an A record for the root, a CNAME for subdomains, or full nameserver delegation), then verify ownership and wait for the platform to issue a TLS certificate. Most of that wait is automatic. Once DNS propagates, which usually takes a few hours though occasionally can take longer, your site answers securely on your own domain.
TL;DR:
- Use an A record for a root domain and a CNAME for a subdomain; if root CNAMEs are unsupported, choose ALIAS, ANAME, or flattening.
- Delegate nameservers only after copying existing MX, SPF, DKIM, and DMARC records into the new zone, then send a test email.
- DNS changes usually propagate within a few hours but can take up to 48 hours; compare two checkers before changing records again.
- An HTTP file challenge works only after the domain resolves to the platform, while wildcard certificates generally need DNS validation for certificate issuance.
- When moving DNS providers with DNSSEC enabled, coordinate new DS records with your registrar; otherwise, resolution can fail for the whole domain.
Table of Contents
- Add the domain in your platform dashboard
- Configure DNS at your registrar: records and patterns
- Verify the domain: TXT records, ACME challenges, and waiting for TLS
- Troubleshooting common setup problems and quick diagnostics
- Advanced DNS notes: wildcards, CAA, and delegation patterns
- How we support custom domain setup on Aria
- When to delegate nameservers versus keep your own DNS
- A simpler way to manage your domain and everything behind it
- FAQ
- Sources
Add the domain in your platform dashboard
Every platform worth using has a settings area called something like "Domains," "Custom Domain," or "Site Settings." That's where the process starts, and it's also where the platform tells you exactly what it needs from your DNS.
Once you type in your domain and confirm it, the platform typically responds in one of three ways:
- It gives you one or more IP addresses to use in an A record (for root domains like example.com).
- It gives you a hostname to use in a CNAME record (for subdomains like shop.example.com).
- It offers an automatic setup option where you briefly authorize a login to your registrar, letting the platform write the records for you.
Some platforms also offer nameserver delegation as an alternative to manual records, which hands the entire zone over to the platform. Whichever path you pick, write down what the dashboard shows you. You'll need those exact values in the next step, and a typo in an IP address or hostname is the single most common reason setups stall.
Configure DNS at your registrar: records and patterns
This is where the setup actually happens. Log into whichever company you bought the domain from and open the DNS management section, sometimes labeled "Zone File" or "DNS Records."
- For a root or apex domain (example.com), use an A record with the host set to
@, pointing to the IP address your platform gave you. - For a subdomain (blog.example.com), use a CNAME record with the host set to
blog, pointing to the hostname your platform gave you. - If your registrar won't allow a CNAME at the root, look for ALIAS, ANAME, or "CNAME flattening," which do the same job while staying compliant with DNS standards for nameserver behavior.
- Never leave both an A record and a CNAME pointing at the same host name. Pick one.
Full nameserver delegation is a bigger decision. It hands your entire zone, every record, not just the one for your site, to a new provider. That's fine if you're starting fresh, but if you already run email through that domain, you need to export your existing MX, SPF, DKIM, and DMARC records first and recreate them in the new zone before the switch goes live. Our partner's guide to verifying an email domain walks through what those records do and why losing one breaks mail delivery.
Pro Tip: Screenshot or copy your current DNS records before changing anything, even if you think you won't need them.
Verify the domain: TXT records, ACME challenges, and waiting for TLS
Verification proves you actually control the domain, and it's also how your platform gets you a TLS certificate so your site loads securely.
- TXT verification: the platform gives you a token to paste into a specific record, often at a label like
_acme-challenge.example.com. Add it exactly as shown, then confirm inside the dashboard. - HTTP-01 challenge: instead of a DNS record, some platforms ask you to place a small file at
/.well-known/acme-challenge/. This method works only when the domain already resolves to the platform's servers. - DNS-PERSIST-01: a newer option from Let's Encrypt that publishes one standing authorization record instead of a fresh TXT entry for every renewal, which cuts down on repeated DNS edits for platforms managing many domains at once.
Most DNS changes propagate within a few hours, though the window can stretch up to 48 hours in rare cases according to IANA's nameserver guidance. You can check progress with a tool like dig or any public DNS checker while you wait for your certificate to issue.
Troubleshooting common setup problems and quick diagnostics
Most stalled setups trace back to one of a handful of causes.
- Check for conflicting records, especially an A record and a CNAME on the same host name, and delete whichever one your platform doesn't require.
- Run
digornslookupagainst your domain to see what's actually being returned, then compare it against what your platform expects. - If results look inconsistent across checks, you may be hitting a cached answer from an old nameserver or a public resolver that hasn't refreshed yet.
- After any nameserver change, confirm your MX, SPF, DKIM, and DMARC records made it into the new zone, then send a test email to verify mail still flows.
Pro Tip: When in doubt, query your domain from two different DNS checkers; a mismatch between them usually points to propagation lag rather than a misconfiguration.
Advanced DNS notes: wildcards, CAA, and delegation patterns
A few situations come up often enough to mention even if you won't need them on day one.
- Wildcard certificates (covering
*.example.com) almost always require a DNS-01 challenge rather than HTTP-01, since there's no single file path that can prove control over every possible subdomain, a pattern confirmed in Let's Encrypt's challenge type documentation. - CAA records tell certificate authorities which ones are allowed to issue certificates for your domain; some platforms will ask you to add one before they'll issue TLS.
- If your main DNS provider is slow to update or lacks an API, you can delegate just the
_acme-challengesubdomain to a faster provider using an NS or CNAME record, which keeps automated renewals running without exposing your whole zone. - If you use DNSSEC, moving providers means coordinating new DS records with your registrar; skipping this step can break resolution for the entire domain, not just the certificate.
How we support custom domain setup on Aria
The custom domain area under site settings gives you two paths: manual records or full nameserver delegation, whichever fits how much DNS you want to manage yourself. Once you add your domain, the platform supplies the verification token, the DNS targets, and automated TLS provisioning, so certificates issue on their own once records check out. If you delegate nameservers and already run email on that domain, export your MX, SPF, DKIM, and DMARC records first, then confirm mail still arrives after the switch. We keep step-by-step checklists in our help resources for anyone who wants the fuller walkthrough.
When to delegate nameservers versus keep your own DNS
If you run email or maintain several custom records on your domain, add only the records your platform requires and leave the rest of your zone alone. If you'd rather hand off DNS entirely and never think about it again, delegation is the simpler route, as long as you export your existing records first. For most creators and solopreneurs, the convenience of delegation outweighs the one-time work of migrating records, especially when the platform copies mail settings over automatically.
— Anastasia
A simpler way to manage your domain and everything behind it
We built Aria so a custom domain setup doesn't have to be its own project. Add your domain, choose manual records or nameserver delegation, and we handle TLS issuance automatically while preserving your existing email setup along the way. Because your business tools already live in one place, you're not stitching together separate DNS and TLS settings across multiple tools.
| Plan | Price |
|---|---|
| Build | $197 per month |
| Grow | $297 per month |
| Scale | $497 per month |
Visit the Aria landing page to compare plans and connect your domain in minutes.
FAQ
Is domain flipping illegal?
Buying and reselling domain names, often called domain flipping, is a legal practice in most jurisdictions as long as you're not infringing on existing trademarks or engaging in cybersquatting. Registering a domain that closely mimics a known brand to resell it at a markup can expose you to legal claims under trademark law. Check your domain name against existing trademarks before purchasing it for resale.
What are the 7 types of domains?
Common domain categories include generic top-level domains like .com and .org, country-code domains like .uk or .de, sponsored domains tied to specific communities, and newer generic extensions like .shop or .app. Definitions of domain types vary by source, so there's no single agreed-upon list. For most website owners, the practical choice comes down to a generic top-level domain versus a country-code one.
How do I set up my own domain?
Buy a domain from a registrar, then add it inside your website platform's dashboard under domain or site settings. Update your DNS records there, using an A record for a root domain or a CNAME for a subdomain, then verify ownership through the TXT record or challenge your platform requests. Most platforms issue a TLS certificate automatically once DNS checks out.
Can I create a custom domain?
Yes, you can connect a custom domain to nearly any modern website or business platform by purchasing the domain through a registrar and pointing its DNS records at your platform. The process usually takes three steps: add the domain, update DNS, and verify ownership. On Aria, we walk you through each step and handle certificate issuance automatically.
Sources
For deeper technical detail beyond what fits in a setup guide, a few primary sources are worth bookmarking.
- Domain Name System (DNS) — IANA nameserver requirements
- DNS-PERSIST-01: A New Model for DNS-based Challenge Validation — Let’s Encrypt