You bought your domain at Namecheap, Porkbun, or Cloudflare. You want to point it to your namemyapp project without moving the registration. Good news: you do not need to transfer anything. You simply connect external domain to namemyapp by updating a few settings at your registrar.
The process has three parts. First, you tell namemyapp which domain you own. Second, you replace your registrar's default external domain nameservers with the pair namemyapp gives you. Third, you import DNS records so existing services like email and subdomains keep working.
Most founders finish the active setup in under fifteen minutes. The rest is propagation time. You cannot speed that up, but you can avoid mistakes that force you to start over.
What You Need Before You Start
Grab two things before you touch any settings. You need your registrar login and a list of every DNS record you currently rely on. Missing a CNAME or MX entry can break your email or a landing page.
Log into your registrar dashboard. Look for an export option labeled something like "DNS Records," "Zone File," or "Advanced DNS." If you cannot export, screenshot every row. You want the type, host, value, and TTL for each entry.
If you run email on this domain, write down every MX, SPF, and DKIM record before you change a single nameserver. Rebuilding mail authentication from memory is not fun.
Check your TTL values. If they are set to 86400 or higher, consider lowering them to 300 twenty-four hours in advance. Lower TTLs expire faster from resolver caches. That makes rollback quicker if something goes wrong.
If your domain is new, you might not have any records to save. That makes the move easier. But if you have been live for months, assume something is hiding in the zone file. Use a lookup tool to double-check.
dig ANY example.com
This surfaces records your registrar may not display in its pretty dashboard. Copy anything that matters into a text file.
How to Connect External Domain to namemyapp
Open your namemyapp dashboard. Navigate to the project you want to link. Click "Add Domain" and type your root domain, such as example.com. The system will give you two nameservers, usually formatted like ns1.namemyapp.com and ns2.namemyapp.com.
Copy both values exactly. Do not add extra periods. Do not mix them with your old registrar defaults. You must replace the entire set, not append to it.
Here is the exact sequence:
- Add the domain inside namemyapp and copy the assigned nameservers.
- Open your registrar's site in a new tab.
- Find the Nameservers or Authoritative DNS section.
- Replace the default entries with
ns1.namemyapp.comandns2.namemyapp.com. - Save, then return to namemyapp and click Verify.
Verification can be instant or take up to an hour. It depends on how quickly your registrar publishes the change and how aggressively local DNS caches hold the old data.
You do not need to move registration. Your annual renewal stays with whoever you paid. You are only delegating DNS authority to namemyapp. Think of it as telling the global directory whom to ask for directions.
Updating External Domain Nameservers
Every registrar hides this panel in a different spot. The table below shows where to look for three popular options.
| Registrar | Path to Nameservers | Typical Propagation |
|---|---|---|
| Namecheap | Domain List → Manage → Domain → Nameservers | 15–30 minutes |
| Porkbun | Domain Management → Edit → Authoritative Nameservers | 10–20 minutes |
| GoDaddy | My Products → DNS → Nameservers | 20–60 minutes |
When you paste in the new external domain nameservers, remove the old ones completely. Running two different sets at once creates a split-brain scenario. Some visitors see your namemyapp site. Others see your old host. Debugging that is painful.
Save the change. Most registrars send a confirmation email. Then wait. You can check progress from your terminal with dig:
dig +short NS example.com
dig +short A example.com
Run the first command every few minutes. When it returns ns1.namemyapp.com and ns2.namemyapp.com, propagation is active. The second command should then resolve to your project's IP or alias.
Do not panic if the site looks fine on your phone but broken on your laptop. Your home router may cache DNS longer than your mobile carrier. Flush local cache or use a mobile hotspot to see the live state.
Use whois example.com to see the raw nameserver delegation. If it lists your registrar, the change has not reached the registry yet. If it lists namemyapp, the internet knows about the switch and you are waiting on resolver caches.
Import DNS Records to Keep Services Alive
Changing nameservers wipes out your old DNS configuration. namemyapp starts you with a clean slate. If you rely on subdomains, email, or third-party verifications, you need to import DNS records into the new panel.
namemyapp supports importing records via BIND zone files or CSV uploads. Look for the import option next to your domain. Select your exported file and map the columns if the parser asks.
Common records to carry over include:
Arecords for root and wildcard redirectsCNAMErecords forwww,app, ordocssubdomainsMXrecords for email routingTXTrecords for SPF, DKIM, and domain verification
After upload, namemyapp shows a preview of what it parsed. Review each row. A common glitch is importing a CNAME on the root domain. That violates DNS rules. Convert root aliases to A records or use an ALIAS if namemyapp supports it.
Set conservative TTLs during the transition. Use 300 seconds for the first forty-eight hours. Once you are confident everything is stable, raise them to 3600 or higher to reduce lookup load.
Test everything before you call it done. Send an email to yourself from the domain. Hit the subdomains in a browser. Check that www redirects where you expect.
Common Mistakes to Avoid
People often leave the registrar's default nameservers in place. They paste the namemyapp pair into the first two slots and leave the other two untouched. That breaks routing in unpredictable ways. Always replace the full set.
Another error is importing records that still point to the old web host. If your A record for @ still resolves to your old host's IP, namemyapp cannot serve the site. Update that root A record to the IP shown in your namemyapp domain settings.
Some founders forget about third-party services. Stripe, Mailgun, and Notion all ask you to verify ownership via TXT or CNAME records. If those disappear during the move, the integrations pause. Keep a checklist of every SaaS tied to your domain.
Timing matters. Do not start this process five minutes before a product launch. Give yourself a buffer. DNS is reliable, but it rewards patience.
FAQ
How long does nameserver propagation take?
Most users see full propagation within thirty minutes. Some registrars push changes to the registry instantly. Others batch updates. Global resolver caches add another variable. If you are still seeing the old site after two hours, check that you saved the nameserver change and did not introduce a typo. You can also test from a different network to rule out local caching.
Will my email stop working when I switch nameservers?
Yes, if you do not import your mail records. The moment you switch external domain nameservers, the old mail routing instructions are gone. Before you make the change, export your MX, SPF, and DKIM records. Import them into namemyapp immediately after verification. Send a test message before you announce the move is complete. If you use Google Workspace, Microsoft 365, or Proton Mail, their setup wizards give you the exact records to preserve.
Can I import DNS records before changing nameservers?
You can preload them into namemyapp, but they will not be live until the nameservers switch. The old registrar still controls the public responses. Preloading simply shortens the gap between delegation and full service. It is a smart safety move for complex zones with many subdomains.
Do I need to transfer my domain registration to namemyapp?
No. Registration and DNS hosting are separate. You can keep renewing at your current registrar forever. You only need to connect external domain to namemyapp by delegating DNS authority. If you ever want to leave, you simply paste your old nameservers back in. Your domain remains yours.