You bought your domain on Namecheap, Cloudflare, or Google Domains. Now you want to point it at your namemyapp project. This guide will show you how to connect external domain to namemyapp, keep your existing DNS records intact, and avoid the downtime that trips up most solo founders.
The process takes about ten minutes of active work. DNS propagation adds another hour or two. You do not need to transfer registration away from your current registrar.
What You Need Before You Start
Gather three things. First, admin access to your domain registrar. Second, a list of your existing DNS records—especially MX records for email and any A or CNAME records pointing to live services. Third, a few minutes when you can tolerate a brief transition window.
Most founders skip the second step. They assume everything will copy over perfectly. Then their transactional email stops working for three hours.
Print or screenshot your current DNS zone before you touch anything. If your email provider is Google Workspace, Zoho, or ProtonMail, those MX values are your lifeline.
Step-by-Step: connect external domain to namemyapp
The dashboard workflow is straightforward. Log into namemyapp, open your project settings, and choose Domains. Click Add Custom Domain, then type the root domain (like example.com) or a subdomain (like app.example.com).
Namemyapp will generate two nameservers for you. They usually look like ns1.namemyapp-dns.com and ns2.namemyapp-dns.com. Write these down. You will paste them into your registrar in the next step.
Do not change your registrar's nameserver fields yet. First, open the namemyapp DNS panel and look for the Import DNS Records button. This is where the magic happens.
- Click Import DNS Records inside the namemyapp dashboard.
- Enter your domain in the import dialog.
- Select your current DNS provider from the dropdown (Cloudflare, Route53, GoDaddy, or Generic).
- Review the fetched records in the preview table.
- Click Confirm Import to stage them in your namemyapp zone.
The importer pulls A, AAAA, CNAME, MX, TXT, and SRV records. It does not guess at wildcard records. If you rely on *.example.com, add that CNAME or A record manually after the import finishes.
Lower Your TTLs the Day Before
Time-to-live values tell recursive resolvers how long to cache a DNS answer. High TTLs delay your ability to fix a mistake quickly.
If your current records use a TTL of 86400 seconds (24 hours), a bad MX record could take a full day to purge from global caches. Drop every TTL to 300 seconds at least twenty-four hours before you change nameservers.
Most registrars let you bulk-edit TTLs. Look for a_ttl, mx_ttl, or a global default in the DNS management UI. Save the changes. Wait. This one preparatory step turns a potential day-long outage into a five-minute blip.
Updating Your External Domain Nameservers
Now you switch the delegation. This is the only step that affects the live internet.
Log into your registrar. Find the Nameservers section—sometimes buried under DNS settings, sometimes under Domain Management. Switch from the default setup to Custom DNS. Delete the existing entries. Add the two namemyapp nameservers exactly as they appeared in your dashboard.
Save and wait. Most TLDs propagate within an hour. .io and .co can be slower. Do not panic if dig NS example.com still shows your old provider after five minutes.
dig NS example.com +short
dig NS example.com @ns1.namemyapp-dns.com +short
Run the first command every ten minutes. Once it returns the namemyapp nameservers, the switch is live.
How to Import DNS Records After the Switch
Some founders import records before changing nameservers. Others do it after. Both work, but the timing matters for accuracy.
If you import early, namemyapp fetches from your current live zone. That is usually fine. But if your old provider stops serving DNS the moment you change nameservers, any records you forgot to import will vanish until you add them manually.
Here is a comparison of the two approaches:
| Approach | When to Use | Risk Level | Best For |
|---|---|---|---|
| Pre-import | Stable zone, many records | Low | Teams with complex email + SaaS routing |
| Post-import | Simple zones, few records | Medium | Solo hackers with just A + CNAME |
| Hybrid | Critical email infrastructure | Lowest | Founders who cannot afford MX downtime |
The hybrid method works like this. Import everything before the switch. Change nameservers. Wait for propagation. Then run a second import to catch any last-minute changes your old provider might have cached.
Double-check these critical record types after any import:
- MX records — Email dies without them.
- TXT records — SPF, DKIM, and domain verification tokens live here.
- CNAME flattening — Some registrars flatten
wwwCNAMEs to A records. Namemyapp preserves the CNAME if possible.
Verifying the Handoff
Propagation is not binary. Your laptop might see the new nameservers while a user's phone in Berlin still hits the old ones. Test from multiple angles.
Use a global DNS checker like whatsmydns.net to watch NS records spread. For deeper validation, inspect specific records:
dig MX example.com +short
dig TXT _dmarc.example.com +short
dig A example.com +short
If any record is missing, add it manually in the namemyapp DNS editor. The editor accepts standard BIND-style inputs. An MX record looks like 10 mail.example.com. with the trailing dot.
SSL provisioning starts automatically once namemyapp detects the nameserver change. Force a recheck by clicking Verify Domain in the dashboard if the certificate has not appeared within thirty minutes.
FAQ
Do I have to transfer my domain registration to namemyapp?
No. You keep your registrar. You only change the external domain nameservers to the ones namemyapp provides. Your billing, WHOIS privacy, and renewal settings stay exactly where they are.
How long does it take to import DNS records?
The automated fetch takes under thirty seconds for zones with fewer than fifty records. Complex zones with hundreds of records might need two minutes. Manual review adds whatever time you spend comparing the preview table to your backup screenshot.
Will changing nameservers break my email?
Only if you forget to import DNS records that include your MX entries. The namemyapp importer detects MX records automatically, but you should still verify them in the preview step. If you use Google Workspace, your MX priorities should read 1 ASPMX.L.GOOGLE.COM. and so on. Add them by hand if the import misses even one.
Can I revert if something goes wrong?
Yes. Keep your old nameserver values in a text file. If the handoff fails, paste them back into your registrar. DNS reverts within the same propagation window—usually under an hour. Your old zone remains cached at the previous provider for at least the original TTL duration, so reverting is low-risk.
Does namemyapp support DNSSEC?
Not for externally registered domains using delegated nameservers. You must disable DNSSEC at your registrar before changing nameservers. Look for a DS record management page and remove any published keys. Re-enable it later if namemyapp adds support.