Downtime during a transfer almost always has the same cause: the domain moves before its DNS records do, and for a while nobody answers for the zone. The fix is to treat DNS and registration as two separate moves and do them in order. DNS hosting at Himk is a separate product from domain registration, which makes this easy.
Step 1. Copy your records to Himk DNS
Add the zone in the Himk panel and recreate every record from your current provider: A, AAAA, CNAME, MX, TXT and anything else. Pay special attention to mail (MX, SPF, DKIM) and verification TXT records, which are easy to miss.
Before you switch anything, ask Himk directly and compare the answers with what your current provider returns:
dig +short MX example.am @ns1.himk.am
dig +short MX example.amStep 2. Switch the name servers
At your current registrar, replace the name servers with ns1.himk.am and ns2.himk.am. Both providers now hold the same records, so it does not matter which one a resolver asks while caches update. See Point name servers to Himk for details.
Keep the old zone for now Resolvers may keep the old name servers in cache for up to 48 hours. Leave the records at your old provider until the switch has fully spread, and do not change records in only one place during that time.
Step 3. Transfer the domain
Once traffic is served by Himk DNS, move the registration itself:
- At the current registrar, remove the transfer lock and request the transfer code if one is required.
- In the Himk panel, start the transfer and enter the code.
- Confirm the transfer if your current registrar asks you to.
The name servers stay the same during the transfer, so your site and mail keep working. The exact steps for each TLD are in the domain transfer guide.
Step 4. Lock it and check the details
After the transfer completes, turn the transfer lock back on and review the domain’s WHOIS contact profile. Each domain has one profile, so a single update keeps it correct. Now you can safely delete the zone at your old DNS provider.