You bought a domain at Namecheap, GoDaddy, or Cloudflare. Now you want to point it at namemyapp so your landing page, waitlist, or MVP actually resolves. The process is straightforward once you understand the two halves: changing external domain nameservers and choosing what to import dns records for.
This tutorial walks through the exact steps. No fluff, no upsell. Just the sequence that works for most solo founders.
The core idea: your registrar still owns the domain. namemyapp becomes the service that answers DNS queries for it. That split is normal and healthy. You can reverse it anytime.
What "Connect" Actually Means
When you connect external domain to namemyapp, you are not transferring ownership. The registrar keeps your WHOIS record, your renewal billing, and your contact email. What changes is the authoritative nameserver setting.
DNS works like a phone book. The registrar publishes a pointer that says "ask these servers about this domain." By default, that pointer goes to the registrar's own nameservers. When you connect to namemyapp, you repoint that pointer to namemyapp's nameservers.
One domain can only have one set of authoritative nameservers. You cannot split traffic between Namecheap DNS and namemyapp DNS for the same apex domain.
That rule trips up founders who want "just the root domain on namemyapp and the rest on Cloudflare." It doesn't work that way. You pick one DNS provider.
What You Get After Connecting
Once namemyapp is authoritative, it can:
- Serve your landing page at
example.comandwww.example.com - Handle email forwarding or catch-all addresses
- Manage subdomains like
app.example.comordocs.example.com - Auto-provision SSL certificates without you touching a
.pemfile
The tradeoff: you manage all DNS records inside namemyapp, not at your registrar. For most early-stage projects, that's a feature.
Step 1: Locate Your Registrar's Nameserver Settings
Every registrar buries this in a slightly different menu. Here's where to look for the common ones:
| Registrar | Menu path | Typical propagation time |
|---|---|---|
| Namecheap | Domain List → Manage → Nameservers | 30 min to 4 hours |
| GoDaddy | Domain Portfolio → DNS → Nameservers | 15 min to 2 hours |
| Cloudflare Registrar | Domain → DNS → Nameservers | 5 min to 1 hour |
| Porkbun | Domain Management → Details → Nameservers | 10 min to 2 hours |
Propagation times vary because ISPs cache DNS responses. Some resolvers respect TTLs. Others ignore them. Don't panic if your domain doesn't resolve for everyone at the same moment.
Custom vs. Default Nameservers
You need the custom nameserver option, not the registrar's default. The exact label differs:
- Namecheap calls it "Custom DNS"
- GoDaddy calls it "Change Nameservers"
- Porkbun calls it "Authoritative Nameservers"
Select that option, then enter the two or three nameservers namemyapp provides. They look like ns1.namemyapp.com and ns2.namemyapp.com. Some setups include a third for redundancy.
Step 2: Enter namemyapp's Nameservers
Log into your namemyapp dashboard. Open the domain you're connecting. You'll see a panel titled "Nameservers" or "DNS Settings" with the exact values to copy.
They'll resemble:
ns1.namemyapp.com
ns2.namemyapp.com
ns3.namemyapp.com
Copy all of them. Paste them into your registrar's custom nameserver fields. Save.
At this point, your registrar no longer answers DNS queries for the domain. It only tells the world where to ask. That's the entire "connect external domain to namemyapp" step.
What Not to Do
Don't enter namemyapp nameservers in the "DNS Records" section of your registrar. That section is for A records, CNAMEs, MX records. Nameservers go in their own field. Mixing them up is the most common mistake.
Also, don't leave one registrar nameserver and one namemyapp nameserver. That creates a split-brain setup where some visitors hit the old DNS and some hit the new one. Use all namemyapp nameservers or none.
Step 3: Import DNS Records into namemyapp
Now you have a choice. You can:
- Import existing records from your old DNS provider
- Start fresh and add only what you need
If your domain already has email (Google Workspace, Zoho, Fastmail) or subdomains pointing at live services, you need to import those records. Otherwise you'll break email and subdomain routing.
How to Export from Common Providers
Before you switch nameservers, export your current DNS zone. Most providers offer a "Export DNS" or "Download Zone File" option.
- Cloudflare: DNS → Records → Export
- Namecheap: Advanced DNS → Export
- GoDaddy: DNS → Download Zone File
- Route 53: Hosted Zone → Export
Save the file as .txt or .csv. It contains every record type: A, AAAA, CNAME, MX, TXT, NS, SRV.
Import into namemyapp
In your namemyapp domain dashboard, look for "Import DNS Records" or "Bulk Import." Upload the zone file. namemyapp parses it and shows you a preview of what it found.
Review the preview carefully. Look for:
- Stale records pointing at old hosts or decommissioned services
- Duplicate records that will cause conflicts
- Missing records for services you still use
A zone file export from some registrars includes their own default records, like parking pages or verification TXT entries. Importing those into namemyapp can cause odd behavior. Delete anything you don't recognize as yours.
If You Don't Import
If you skip the import and your domain had email, here's what breaks:
- Incoming email bounces because there's no
MXrecord - SPF and DKIM checks fail because
TXTrecords are gone www.example.comreturns an error because noCNAMEorArecord exists
That's why the import step matters. It's not optional if you had any existing DNS configuration.
Step 4: Verify the Connection
After saving nameservers at your registrar and importing records into namemyapp, wait. Then verify.
Use dig from your terminal:
dig NS example.com
You should see namemyapp's nameservers in the answer section. If you still see your registrar's nameservers, the change hasn't propagated yet.
Check a specific record:
dig A example.com
This shows whether the A record you imported or created in namemyapp is being served. If it returns NXDOMAIN, wait longer or re-check your namemyapp DNS panel.
Propagation Checklist
Here's a numbered sequence to follow when something looks wrong:
- Confirm you saved the nameserver change at your registrar. A preview page isn't a save.
- Check that you entered all namemyapp nameservers, with no typos.
- Verify the domain in namemyapp shows "Active" or "Connected," not "Pending."
- Run
dig NS example.comand confirm namemyapp nameservers appear. - Check individual records with
dig A example.comordig MX example.com. - If records are correct but the site still doesn't load, clear your local DNS cache with
sudo dscacheutil -flushcacheon macOS oripconfig /flushdnson Windows.
Most issues are typos, unsaved changes, or impatience. The DNS system is slow by design.
Common Pitfalls and How to Avoid Them
Apex vs. WWW Confusion
Your example.com apex domain needs an A record. Your www.example.com subdomain needs either a CNAME pointing to the apex or its own A record. namemyapp's default setup usually handles both, but if you import a zone file that lacks one, you'll see a broken www or a broken apex.
Email After the Switch
If you use Google Workspace, your MX records point to Google's servers, not namemyapp's. That's correct. namemyapp is authoritative for DNS, but it doesn't host your email. Keep those MX records intact during import.
The same applies to TXT records for SPF and DKIM. If you delete them, your email lands in spam folders.
Subdomains for Other Tools
Many founders run their app on Vercel or Netlify while their marketing site lives on namemyapp. That's fine. You create a CNAME for app.example.com pointing to cname.vercel-dns.com or Netlify's equivalent. The key is that all those records live in namemyapp now, not at your registrar.
FAQ
How long does it take to connect external domain to namemyapp?
The nameserver change itself takes minutes to save. Propagation takes anywhere from 15 minutes to 48 hours, depending on your registrar and the ISPs involved. Most users see resolution within 1 to 4 hours. You can speed up local testing by flushing your DNS cache.
Do I need to transfer my domain to namemyapp?
No. Connecting external domain to namemyapp is a nameserver change, not a domain transfer. Your registrar continues to handle renewals and WHOIS. You can reverse the connection at any time by changing nameservers back.
What happens to my email when I switch nameservers?
If you import your MX and TXT records correctly, email keeps working. The key is exporting your zone file before you switch and importing it into namemyapp after. If you skip that step, email breaks because there are no MX records pointing to your mail provider.
Can I use namemyapp for DNS but host my app elsewhere?
Yes. You can point subdomains like app.example.com to Vercel, Netlify, Render, or any host using CNAME or A records. namemyapp manages the DNS, but it doesn't force you to host everything on its infrastructure.
What if I only want to import some DNS records?
You can import a zone file and then delete records you don't want. Or you can skip the import entirely and add records manually. The import is a convenience, not a requirement. Just make sure every record you need exists in namemyapp before you switch nameservers.