Migrating Your Domain to iWebVault: Transfer vs. Nameserver Change

“Migrating your domain” sounds like one thing — but it’s actually two different operations with different effects, different costs, and different reasons to do them. Understanding the difference is the difference between a smooth migration and a confused multi-week ordeal where your site is unreachable.

The two operations, in one sentence each

• Domain transfer — moving the registration of your domain from one registrar to another. Affects WHOIS, billing, and who controls the domain. The domain itself stays the same.
• Nameserver change — telling the world that another set of servers answers DNS questions for your domain. Affects where your site and email are hosted. The registrar stays the same.

The two are independent. You can change nameservers without transferring; you can transfer without changing nameservers. Most customers only need to change nameservers.

When you only need a nameserver change

If you’re already happy with your current registrar (Namecheap, Cloudflare, GoDaddy, etc.), you don’t need to transfer the domain to use iWebVault hosting. Just change the nameservers:

• ns1.iwebvault.com
• ns2.iwebvault.com

This tells the global DNS system to ask iWebVault for the A/MX/TXT records for your domain. Your hosting works immediately (after propagation), your site loads, your email flows — and your registrar relationship stays exactly as it was.

Stick with nameserver change only if:

• Your current registrar’s pricing is competitive (most are similar within a couple of dollars per year).
• You’re happy with their interface, customer service, and policies.
• You don’t need WHOIS privacy or it’s already included for free.
• You don’t want to consolidate registrar billing under iWebVault.

This is the right path for the majority of customers.

When transferring the domain makes sense

Move the registration to iWebVault if:

• You want all your services billed in one place. Hosting + domain in one client area, one renewal date, one payment.
• Your current registrar is unreliable. Slow support, frequent outages, suspect security practices.
• You want anonymous registration. Some registrars charge for WHOIS privacy; we include it.
• You want anonymous payment for the domain. Pay for renewal via crypto, no card trail. See our anonymous payment guide.
• Your domain is at risk. If your account at another registrar has been compromised or you’re worried about a takedown attempt, moving to an offshore registrar can be part of your defensive strategy.

Note: the domain transfer is a separate cost from hosting — typically one year of renewal added to your account at the time of transfer.

How to change nameservers (5 minutes)

1. Log into your current registrar’s control panel.
2. Find the domain in question.
3. Look for “Nameservers”, “DNS”, “DNS Management”, or similar. (The menu name varies by registrar.)
4. Change from “Default” / “Registrar’s nameservers” / “Parking” to “Custom nameservers”.
5. Enter:
   • ns1.iwebvault.com
   • ns2.iwebvault.com
6. Save changes.

DNS propagation typically completes within an hour but can take up to 24-48 hours globally. Test with: whatsmydns.net — enter your domain, select “NS”, check whether ns1.iwebvault.com appears worldwide.

How to transfer your domain

Domain transfer is more involved. Plan for 5-10 days total (most of which is waiting).

Prerequisites

• Domain at least 60 days old at the current registrar. ICANN forbids transfers within 60 days of registration or a previous transfer. Wait it out.
• Domain unlocked. Most registrars set a “transfer lock” by default — disable it before initiating transfer.
• EPP code (also called Auth Code or Authorization Code) — a one-time password your current registrar provides to authorize the transfer.
• Email access to the WHOIS registrant email. The transfer process sends approval emails there.

The transfer steps

1. At your current registrar, disable the transfer lock.
2. Request the EPP code — usually emailed to the registrant address. Save it.
3. If WHOIS privacy is enabled, disable it temporarily — some registries can’t process transfers with privacy enabled.
4. At iWebVault’s domain section, initiate a transfer. Enter the domain and EPP code.
5. Pay the transfer fee (typically the cost of one year’s renewal — and that year is added to your domain’s lifespan).
6. Approve any verification email that gets sent. Some TLDs require explicit owner approval at both registrars.
7. Wait. The transfer completes automatically after 5-7 days unless explicitly denied.

Once complete, the domain shows up in your iWebVault client area. Re-enable WHOIS privacy, set up renewal preferences, you’re done.

What stays the same, what changes

Common transfer gotchas

“Domain is less than 60 days old.” ICANN rule, no way around. Just wait the days.

“Domain was transferred within the past 60 days.” Same 60-day rule applies after any recent transfer. Wait.

EPP code rejected. Codes are case-sensitive and sometimes contain characters that look like other characters (0 vs O, l vs 1). Re-request and copy carefully.

Transfer email goes to old/deleted email. The WHOIS registrant email is where transfer-approval emails go. If you don’t have access to that mailbox, update WHOIS at the current registrar first, wait 24 hours, then initiate transfer.

Site goes down during transfer. It shouldn’t — nameservers are independent of registration. If you’ve already changed nameservers, the site loads from iWebVault regardless of whether the registration has finished transferring.

Some TLDs aren’t transferable. Country-specific TLDs (.com.au, .de, .fr) sometimes have additional requirements (proof of residence in the country, specific documentation). Check the TLD’s policy before assuming a transfer is possible.

What’s next

• Configure your DNS records after migration: DNS records explained.
• Site not loading after a nameserver change? Domain not resolving troubleshooting.
• Setting up email on the migrated domain? Email setup in cPanel.

For most customers, nameserver change is enough — your hosting works, your registrar relationship continues, no transfer cost. Reserve domain transfers for cases where consolidating billing or upgrading privacy matters.