You bought a domain at Namecheap, GoDaddy, or Cloudflare. Now you want namemyapp to handle the branding, the name validation, and the domain score. The good news: you don't have to transfer the domain. You just need to connect external domain to namemyapp and point the right records at us.
This tutorial covers the full path. We'll walk through adding your domain inside namemyapp, choosing between nameserver delegation and a simple CNAME, and importing your existing DNS records so nothing breaks when you switch.
Most people finish this in under 20 minutes. Some finish in 10. The slow part is waiting for DNS propagation, not the setup itself.
What "Connecting" Actually Means
Connecting a domain is not the same as transferring it. Your registrar still owns the domain. You still renew it there. You still pay the registrar's price.
What changes is where the domain points.
When you connect external domain to namemyapp, you're telling the internet: "For this domain, use namemyapp's infrastructure for routing, validation, and DNS." Your registrar stays in the loop, but namemyapp becomes the operational layer.
There are two ways to do this:
- Nameserver delegation — you point your domain's nameservers at namemyapp's nameservers. We then serve all DNS records for the domain.
- CNAME delegation — you keep your current DNS provider and add a CNAME record that points a specific hostname at namemyapp.
Both work. The right choice depends on whether you want namemyapp to become your full DNS host or just a validation layer.
Before You Start: Gather What You Have
You need three things before you touch any settings:
- Your registrar login. That's Namecheap, GoDaddy, Porkbun, Cloudflare Registrar, or wherever the domain lives.
- Access to your current DNS zone. If you use Cloudflare DNS, that's a separate login from Cloudflare Registrar. Don't mix them up.
- A list of existing DNS records. We'll cover how to import DNS records shortly, but having a mental map helps.
If you switch nameservers without importing existing records, your email, subdomains, and integrations will silently break. MX records, TXT verification records, and CNAMEs for help desks are the usual casualties.
Option A: Full Nameserver Delegation
This is the cleanest long-term setup. namemyapp becomes your DNS provider, and you manage everything from one dashboard.
Step 1: Add the Domain in namemyapp
Log in to your namemyapp dashboard. Go to Domains and click Add Domain.
Enter the domain exactly as registered, without https:// or www. For example: northstar.dev, not https://northstar.dev.
namemyapp will run a quick availability and format check. If the domain is valid and not already claimed by another account, you'll land on the connection screen.
Step 2: Choose Nameserver Delegation
On the connection screen, select Nameserver delegation. namemyapp will show you two or more nameservers. They look something like:
ns1.namemyapp.com
ns2.namemyapp.com
Copy both. You'll paste them at your registrar.
Step 3: Update Nameservers at Your Registrar
Every registrar buries this in a different place.
- Namecheap: Domain List → Manage → Nameservers → Custom DNS
- GoDaddy: Domain Portfolio → DNS → Nameservers → Change Nameservers
- Porkbun: Domain Management → Details → Nameserver Settings
- Cloudflare Registrar: You can't change nameservers on a Cloudflare-registered domain. You'll need Option B below.
Paste the namemyapp nameservers and save.
Step 4: Import DNS Records
This is the step people skip, and it's the step that causes the most support tickets.
Before you switch nameservers, go to your current DNS provider and export the zone file. Most providers have an Export button that downloads a BIND-format file. If yours doesn't, take screenshots of every record.
Then in namemyapp, go to Domains → Your Domain → DNS → Import. Upload the zone file or paste the records manually.
namemyapp will parse the file and show you a preview of what it's about to import. Check the preview carefully. Look for:
- MX records for email
- TXT records for SPF, DKIM, and domain verification
- CNAME records for
www,mail, or third-party services - A records for your root domain and any subdomains
Import DNS records before you switch nameservers. If you switch first and import later, your domain will have a window where it resolves to nothing.
Step 5: Verify the Connection
Back in namemyapp, click Verify Connection. We'll check that your domain's nameservers match ours and that the zone file is serving correctly.
Propagation can take anywhere from a few minutes to 48 hours, though most registrars update within 2–4 hours. You can check progress with:
dig NS northstar.dev +short
If the output shows ns1.namemyapp.com and ns2.namemyapp.com, the delegation is live.
Option B: CNAME Delegation (Keep Your Current DNS)
If your registrar doesn't allow nameserver changes, or you want to keep DNS at Cloudflare or AWS Route 53, use CNAME delegation instead.
Step 1: Add the Domain in namemyapp
Same as Option A. Go to Domains → Add Domain and enter the domain.
Step 2: Choose CNAME Delegation
Select CNAME delegation on the connection screen. namemyapp will generate a unique target hostname for your domain. It looks like:
northstar-dev.verify.namemyapp.com
Copy that value.
Step 3: Add the CNAME at Your DNS Provider
Go to your current DNS provider and add a new CNAME record.
- Host:
_namemyappor the specific hostname namemyapp shows you - Value:
northstar-dev.verify.namemyapp.com - TTL: Leave at default or set to
3600
Save the record.
Step 4: Verify
Back in namemyapp, click Verify Connection. We'll check for the CNAME record and confirm it resolves.
CNAME verification is usually faster than nameserver delegation because you're only adding one record, not changing the entire zone. Most verifications complete in under 15 minutes.
Importing DNS Records: The Detailed Walkthrough
Whether you choose Option A or Option B, you'll eventually want namemyapp to understand your full DNS picture. Even with CNAME delegation, importing your zone gives namemyapp better data for domain scoring and conflict detection.
Here's the exact process to import DNS records into namemyapp.
Export from Your Current Provider
Log in to your current DNS provider. Look for an Export or Download Zone File option. If you're on Cloudflare:
- Go to your domain → DNS → Settings
- Click Export DNS Records
- Save the file
If you're on Namecheap:
- Domain List → Manage → Advanced DNS
- Look for Export in the top-right
- Save the file
If your provider has no export option, create a manual list. A spreadsheet works fine. Columns: Type, Host, Value, TTL, Priority (for MX).
Import into namemyapp
In namemyapp, go to Domains → Your Domain → DNS → Import.
Upload the zone file or paste your manual list. namemyapp supports standard BIND format, which looks like:
northstar.dev. 3600 IN A 192.0.2.10
northstar.dev. 3600 IN MX 10 mail.northstar.dev.
www.northstar.dev. 3600 IN CNAME northstar.dev.
northstar.dev. 3600 IN TXT "v=spf1 include:_spf.google.com ~all"
The parser will map each record to the right field. Review the preview before confirming.
What to Watch For
Not every record needs to come over. Here's a quick table of what to import and what to leave behind:
| Record Type | Import? | Why |
|---|---|---|
| A / AAAA | Yes | Root domain and subdomain routing |
| CNAME | Yes | www, mail, and third-party service aliases |
| MX | Yes | Email delivery. Missing MX = no email |
| TXT (SPF, DKIM) | Yes | Email authentication and domain verification |
| TXT (old provider verification) | No | Stale verification tokens from previous services |
| NS | No | namemyapp manages these automatically |
| SOA | No | Auto-generated by namemyapp |
Stale TXT records are the most common cause of "it worked before but now it's broken" reports. If a TXT record references a service you no longer use, don't import it.
Common Mistakes and How to Avoid Them
Switching Nameservers Before Importing
This is the big one. You switch nameservers, your old DNS provider stops serving records, and namemyapp has an empty zone. Email bounces. Subdomains die. The site goes down.
The fix is simple: import first, switch second.
Forgetting the www CNAME
Your root domain might resolve fine, but www goes nowhere. Always check that a CNAME or A record exists for www.
Leaving Old Nameservers in the Mix
Some registrars let you add nameservers without removing the old ones. That creates a split-brain DNS situation where some resolvers get old records and some get new ones. Remove old nameservers completely.
Setting TTL Too High
If your old records have a TTL of 86400 (24 hours), changes will take a full day to propagate everywhere. Before you switch, lower TTLs on critical records to 300 or 600. Wait for the old TTL to expire, then make your changes.
Ignoring DNSSEC
If you have DNSSEC enabled at your current provider, you must disable it before switching nameservers. Otherwise, resolvers will reject the new nameservers as invalid. Disable DNSSEC at your registrar, wait for it to propagate, then switch.
How namemyapp Handles External Domain Nameservers
When you connect an external domain, namemyapp doesn't take ownership. It takes operational control, and only for the parts you delegate.
If you choose nameserver delegation, namemyapp becomes the authoritative DNS provider. That means we serve all records, handle DNSSEC signing, and provide uptime monitoring.
If you choose CNAME delegation, your external domain nameservers stay authoritative. namemyapp only receives a validation signal through the CNAME record. This is less powerful for scoring, but it's also less invasive.
Both approaches are valid. The choice comes down to how much DNS control you want to consolidate.
Here's the decision framework in three bullets:
- You want one dashboard for everything: Choose nameserver delegation.
- You're happy with your current DNS provider: Choose CNAME delegation.
- You need advanced DNS features like geo-routing or custom load balancing: Keep your current provider and use CNAME delegation.
FAQ
How long does it take to connect an external domain to namemyapp?
The setup itself takes 10–20 minutes. DNS propagation can take anywhere from a few minutes to 48 hours, depending on your registrar and your old TTL settings. CNAME verification is usually faster than nameserver delegation.
Do I need to transfer my domain to namemyapp?
No. Connecting is not transferring. Your domain stays at your current registrar, and you keep paying the registrar's renewal price. namemyapp only handles DNS and validation.
Can I import DNS records after I've already switched nameservers?
Yes, but you'll have a gap where your domain resolves to nothing. If you've already switched, import your records immediately. If you haven't switched yet, import first.
What happens to my email if I switch nameservers?
If you import your MX records correctly, email keeps working. If you skip the import, email bounces. Always check MX records before and after the switch.
Does namemyapp support DNSSEC?
Yes, when you use nameserver delegation, namemyapp handles DNSSEC signing automatically. If you have DNSSEC enabled at your current provider, disable it there before switching.
Can I connect a subdomain instead of a root domain?
Yes. namemyapp supports connecting subdomains like app.northstar.dev using CNAME delegation. The process is the same, but you'll add the CNAME at the subdomain level rather than the root.
What if my registrar doesn't allow nameserver changes?
Use CNAME delegation instead. Cloudflare Registrar, for example, doesn't allow custom nameservers, but CNAME delegation works fine.