How to Connect External Domain to namemyapp and Import DNS Records

You bought a domain on Namecheap, GoDaddy, or Cloudflare. Now you want to point it at namemyapp without losing the DNS records you already configured. This tutorial walks through the exact steps to connect external domain to namemyapp, import dns records, and avoid the usual downtime traps.

The process has three parts: adding your domain inside namemyapp, copying your existing DNS setup, and switching external domain nameservers. Each part takes a few minutes. The full migration usually finishes within an hour, though DNS propagation can stretch to 24 hours in rare cases.

You do not need to transfer your domain registration. You keep your registrar. namemyapp just becomes the DNS host and app-serving layer.

Before You Start: Gather What You Need

You will need three things open in separate tabs:

Your external registrar's DNS management page
Your namemyapp dashboard
A plain text file or spreadsheet for copying records

Most registrars bury DNS settings under a menu called "DNS Management," "DNS Zone," or "Advanced DNS." If you use Cloudflare as your registrar, the records live under the DNS tab for your domain. If you use Namecheap, look under "Domain List" → "Manage" → "Advanced DNS."

Rule

Copy every record type you see. A records, AAAA records, CNAMEs, MX records, TXT records, SRV records. If you skip the TXT records, you will break email authentication. If you skip MX, email stops arriving.

You are not "moving" records in a destructive way. You are recreating them inside namemyapp, then flipping nameservers. Until the flip, your old DNS host keeps serving traffic. That gives you a rollback path.

Step 1: Add Your Domain Inside namemyapp

Enter the exact domain you registered externally, for example myapp.dev or getlaunchpad.io. Do not add www here. namemyapp treats the root domain and www as separate records you configure later.

Choose the project you want this domain attached to. If you have not created a project yet, namemyapp will prompt you to create one. A project is just a container for your app's settings, environment variables, and deployment targets.

After you click Continue, namemyapp shows a screen titled "Configure DNS." This is where the import work happens.

What namemyapp Shows You

The configuration screen lists two or three nameserver values. They look like:

text

ns1.namemyapp.com
ns2.namemyapp.com
ns3.namemyapp.com

Copy these. You will paste them into your external registrar later.

Below the nameservers, you will see a DNS record table. It starts mostly empty, with maybe a placeholder A record pointing to namemyapp's default IP. Do not worry about that yet.

Step 2: Import DNS Records from Your External Host

Now comes the part people rush. Open your external registrar's DNS page and copy every record into namemyapp's table.

Here is a real example from a typical Namecheap zone for a domain using Google Workspace email:

Record Type	Host	Value	TTL
A	@	76.76.21.21	300
CNAME	www	myapp.vercel.app	300
MX	@	ASPMX.L.GOOGLE.COM	3600
MX	@	ALT1.ASPMX.L.GOOGLE.COM	3600
TXT	@	v=spf1 include:_spf.google.com ~all	300
TXT	google._domainkey	k=rsa; p=MIGfMA0GCSq...	300
CNAME	autodiscover	autodiscover.mail.google.com	3600

Your zone will look different. The point is that you copy the host, value, and TTL for each row into the namemyapp table.

How to Add Records in namemyapp

Click Add Record in the namemyapp DNS table. A small form appears.

For the A record above, you would set:

Type: A
Name: @
Value: 76.76.21.21
TTL: 300

Then click Save. Repeat for each record.

A few notes on record naming:

Some registrars use @ for the root domain. namemyapp also uses @.
Some registrars leave the host field blank for root records. Treat blank as @.
If your registrar shows www as the host, enter www in namemyapp. Do not enter www.myapp.dev.

For MX records, you may also need a priority value. namemyapp's MX form includes a Priority field. Copy the priority number from your external host. Google Workspace MX records typically use priorities 1, 5, 5, 10, 10.

For TXT records, copy the full value including quotes if your registrar shows them. namemyapp strips unnecessary quotes automatically, but it is safer to paste exactly what you see.

Importing via Zone File (Optional)

If your external host lets you export a BIND zone file, you can speed this up. Namecheap, GoDaddy, and Cloudflare all offer zone export in some form.

A zone file looks like this:

text

$TTL 300
@       IN      SOA     ns1.namecheap.com. admin.namecheap.com. (
                        2024010101 ; serial
                        7200       ; refresh
                        3600       ; retry
                        1209600    ; expire
                        300 )      ; minimum
@       IN      NS      ns1.namecheap.com.
@       IN      NS      ns2.namecheap.com.
@       IN      A       76.76.21.21
www     IN      CNAME   myapp.vercel.app.
@       IN      MX      1 ASPMX.L.GOOGLE.COM.

You cannot upload this file directly to namemyapp yet. But you can read it line by line and recreate each record in the dashboard. The IN keyword just means "Internet." Ignore it. The record type is the third column.

Warning

Do not copy the NS records from your old zone file into namemyapp. Those point to your old DNS host. namemyapp manages its own NS records automatically. Copying old NS records will cause conflicts.

Step 3: Point External Domain Nameservers to namemyapp

Once every record is in namemyapp, go back to your external registrar. Find the nameserver settings. This is usually under a tab called "Nameservers" or "DNS Servers," separate from the DNS records page.

Most registrars default to their own nameservers. For example:

Namecheap uses dns1.registrar-servers.com and dns2.registrar-servers.com
GoDaddy uses nsXX.domaincontrol.com
Cloudflare uses names like ada.ns.cloudflare.com and bob.ns.cloudflare.com

You need to switch from those to the namemyapp nameservers you copied in Step 1.

Select the option for Custom Nameservers or Private Nameservers. Paste the three namemyapp values.

Save the change. Your registrar will show a warning like "Changing nameservers may disrupt service." That is standard boilerplate. Because you already recreated your DNS records in namemyapp, the switch should be seamless.

How Long Does Propagation Take?

DNS propagation is not a single event. It is a cascade of caches expiring at different times.

Typical timelines:

Registrar update: 5–15 minutes for the registrar to publish your new nameservers to the root zone.
Root and TLD servers: 30 minutes to 2 hours for .com, .dev, .io, and similar TLDs to reflect the change.
ISP and resolver caches: Up to 24 hours for some residential ISPs and corporate resolvers.

You can check progress with dig:

bash

dig NS myapp.dev +short

If the output shows ns1.namemyapp.com, ns2.namemyapp.com, and ns3.namemyapp.com, the switch has propagated for that resolver. If it still shows your old nameservers, wait and check again.

You can also use a public DNS checker like dnschecker.org to see propagation across many global resolvers at once.

Step 4: Verify Everything Works

After propagation, run through this checklist:

dig A myapp.dev +short returns the IP you set in namemyapp
dig MX myapp.dev +short returns your email provider's MX records
dig TXT myapp.dev +short returns your SPF record
Your app loads at https://myapp.dev
Email flows in both directions

If email breaks, check that you copied the MX priorities correctly. A missing priority defaults to 0 in some systems, which can cause delivery failures.

If your app does not load, check that the A or CNAME record points to the right place. namemyapp shows a green checkmark next to records it can validate.

Common Mistakes When You Connect External Domain to namemyapp

Several things go wrong often enough to deserve their own section.

Copying Only the A Record

Many people assume the only thing that matters is the A record pointing to their app. Then email breaks. Then SPF and DKIM checks fail. Then subdomains stop resolving.

Copy everything. Every record type. Every host.

Forgetting the www CNAME

Your root domain might work while www.myapp.dev fails. That happens when you forget the www CNAME record. Add it even if you plan to redirect www to root later.

Switching Nameservers Before Importing Records

This is the big one. If you flip nameservers first, your old DNS host stops serving records. namemyapp has nothing in its DNS table. Your domain goes dark.

Always import records first. Then switch nameservers.

Using the Wrong TTL

TTL values under 300 seconds make future changes faster but increase DNS query load. Values over 3600 seconds slow down propagation. Stick with whatever your old host used, unless you have a reason to change.

FAQ

How long does it take to connect external domain to namemyapp?

The setup itself takes 15–30 minutes. DNS propagation takes anywhere from 30 minutes to 24 hours depending on your TLD and the resolver checking. Most domains resolve through namemyapp within 2 hours.

Can I keep my domain registered at Namecheap or GoDaddy?

Yes. namemyapp does not require domain transfer. You keep your registrar and only change the nameservers. Your renewal billing stays with your current registrar.

What happens if I forget to import DNS records before switching nameservers?

Your domain will stop resolving until you add the records in namemyapp. The fix is simple: add the missing records in the namemyapp dashboard. Propagation of the corrected records usually takes under an hour, but the outage window depends on how quickly you notice.