You do not need to transfer your domain to connect external domain to namemyapp. If you bought your URL from Namecheap, porkbun, Cloudflare Registrar, or Google Domains, you can keep it right where it is. We will point your existing domain to our infrastructure using nameservers and then import dns records so nothing breaks.
Most founders assume a custom domain requires a transfer. That is not true. A nameserver change is faster, reversible, and keeps your billing with your current registrar.
Before you start, gather two things. You need access to your registrar's dashboard and a list of your current DNS records. Screenshot your existing setup. If you skip this step, you risk losing a stray MX record or an old CNAME you forgot about.
What you need before you start
Every domain has a home. That home is your registrar. Log into the place where you pay the yearly renewal fee.
Check that your domain is unlocked. Some registrars place a 60-day hold after registration or transfer. You cannot change external domain nameservers while a lock is active. Look for a toggle labeled Registrar Lock or Domain Lock.
Make a list of every service tied to your domain. Email, subdomains for staging, CDN records, and verification tokens for third-party tools all live in DNS. Missing one means a broken service later.
Here is what to collect before you touch anything:
- A full export or screenshot of your current DNS zone from your registrar or current DNS host
- The login credentials for your registrar, including any two-factor authentication method
- A rough timeline of when your site receives the least traffic, in case you need to troubleshoot
If you use Google Workspace, Zoho Mail, or another hosted email provider, your MX records are the most fragile part of this migration. Lose them and inbound mail bounces. Always back them up first.
How to connect external domain to namemyapp
Open your namemyapp dashboard. Navigate to the "Domains" section and click "Add Custom Domain." Enter your root domain, such as example.com. Do not include https:// or www here.
The system will generate a unique pair of nameservers for your project. They usually look like ns1.namemyapp-dns.io and ns2.namemyapp-dns.io. Write these down. You will paste them into your registrar in the next step.
Follow this sequence to avoid confusion:
- Add the domain inside namemyapp and copy the assigned nameservers.
- Open your registrar's DNS or nameserver management page in a new tab.
- Replace the existing nameserver values with the pair from namemyapp. Delete the old entries entirely; do not append.
- Save the changes and wait for the dashboard in namemyapp to confirm the connection.
Propagation is not instant. Your local ISP may cache the old records for hours. Use a tool like whatsmydns.net to check global resolution. If most locations show the new nameservers, you are ready for the next phase.
Updating your external domain nameservers
Nameservers are the address book of the internet. When you switch them, you tell the world to ask namemyapp for directions instead of your old host.
Log into your registrar. Find the page labeled "Nameservers," "DNS Management," or "Custom DNS." Every registrar hides this in a different spot.
Namecheap places it under Domain List > Manage. Cloudflare puts it under DNS > Nameservers. Porkbun uses the Domain Management area.
Replace the current values with the two namemyapp nameservers you copied earlier. Save the changes. Your registrar will show a success message, but that only means the request was submitted.
You can verify progress from your terminal. Run:
dig +short NS example.com
dig +short A example.com
dig +short MX example.com
Swap example.com for your actual domain. The first command shows which nameservers the world sees. The second and third confirm your A and MX records resolve correctly after you import dns records.
How to import DNS records without downtime
This is the step that saves you from a broken site. namemyapp can scan your previous DNS host and import dns records automatically. You trigger this from the domain details page inside our dashboard.
The importer looks for common record types. It pulls A, AAAA, CNAME, MX, TXT, and SRV entries. It does not guess; it reads what was publicly visible before the switch.
Review every imported record manually. Automated imports sometimes grab stale verification records or duplicate entries. Delete anything you do not recognize. Update the IP addresses if your origin server changed.
Here is how common record types map to services:
| Record Type | Typical Use | Import Priority |
|---|---|---|
| A / AAAA | Root domain, web hosting | Critical |
| MX | Email routing | Critical |
| CNAME | Subdomains, CDNs | High |
| TXT | Verification, SPF, DKIM | High |
| SRV | SIP, XMPP, specific apps | Medium |
After the import, wait ten minutes. Then query your records using dig or an online lookup tool. If the results match your old setup but now resolve through namemyapp nameservers, you have succeeded.
Lower your TTL values at your old DNS host 24 hours before you switch. A TTL of 300 seconds tells resolvers to check back frequently. This shrinks the propagation window from hours to minutes.
FAQ
Do I need to transfer my domain to namemyapp?
No. You only need to change your external domain nameservers. Ownership, renewal billing, and WHOIS management stay with your current registrar. This is the difference between parking a car and moving it to a new garage.
How long does it take to import DNS records?
The automated scan usually finishes in under two minutes. Propagation across the internet takes longer. Most records are visible globally within thirty minutes to four hours. Mail records sometimes need up to twenty-four hours to fully settle.
Will my email stop working when I switch nameservers?
It will not stop if you import dns records correctly. The key is ensuring your MX records, along with any SPF and DKIM TXT records, are present in namemyapp before the old nameservers go offline. Always send a test email to yourself after the import finishes.
Can I revert if something breaks?
Yes. Change your nameservers back to the original pair at your registrar. DNS is stateless, and there is no lock-in from a nameserver change. Keep your old DNS records saved in a text file. You can restore them quickly if something feels off.