← Back

Technical Aspects of Domain Transfer and DNS

Technical Aspects of Domain Transfer and DNS

Welcome to Domenemeglerskolen! As the editor, it is my pleasure to guide you through the technical intricacies of domain transfer and DNS – topics crucial for any business owner or investor operating in the digital landscape. A smooth and secure domain transfer is not merely a matter of formalities but a critical process that directly impacts your online presence, email communication, and website availability. Mishandling can lead to downtime, data loss, and, in the worst case, financial repercussions. This article will provide you with a thorough understanding of these technical aspects.

What is Domain Transfer?

Domain transfer, often referred to as domain migration, is the process by which the ownership and/or management of a domain name is moved from one registrar to another, or from one owner to another. It is important to distinguish between changing ownership (which involves a legal transfer of rights) and changing registrars (which is a technical transfer of management). In both cases, DNS settings are central to ensuring a seamless transition.

Understanding DNS: The Foundation of Your Online Presence

DNS (Domain Name System) is the internet's 'phone book'. It translates human-friendly domain names (e.g., domenemegling.dstn.no) into machine-readable IP addresses (e.g., 192.0.2.1). Without DNS, navigating the internet using domain names would be impossible. When you type a domain name into your browser, your computer sends a request to a DNS server to find the associated IP address, which in turn points to the web server where your website is hosted.

Key DNS Records in Domain Transfer:

  • A record (Address Record): Maps a domain name to an IPv4 address. This is the most basic record for pointing your domain to a web server. For example, yourcompany.com points to 192.0.2.42.
  • AAAA record (IPv6 Address Record): Similar to the A record, but maps to an IPv6 address.
  • CNAME record (Canonical Name Record): Used to alias one domain name to another. Often used for subdomains, e.g., www.yourcompany.com pointing to yourcompany.com.
  • MX record (Mail Exchange Record): Specifies which servers are responsible for receiving email for your domain. An incorrect MX record can result in you not receiving emails.
  • NS record (Name Server Record): Indicates which name servers are authoritative for your domain. These are the servers that contain all other DNS records for your domain.
  • TXT record (Text Record): Used for various text information, often for security purposes such as SPF (Sender Policy Framework) and DKIM (DomainKeys Identified Mail) for email authentication, or for domain validation.

The Domain Transfer Process – Step by Step

A typical domain transfer involves several critical steps. To illustrate, let's say you have purchased newdomain.com and wish to transfer it from the Seller's Registrar to your own Registrar:

  1. Unlock the domain: The domain must be unlocked at the current registrar (Seller's Registrar). This prevents unauthorized transfers.
  2. Obtain authorization code (EPP code/Auth code): The seller must obtain this code from their registrar. The code acts as a password confirming that the transfer is authorized. Without this code, the transfer cannot commence.
  3. Initiate transfer with new registrar: You (or your new registrar) start the transfer process by providing the domain name and EPP code to your chosen registrar.
  4. Confirm ownership: An email will often be sent to the domain's administrative contact (WHOIS information) to confirm the transfer. It is crucial that the WHOIS information is up-to-date before the transfer.
  5. DNS migration (the critical point): This is where the technical aspects come in. Before, during, or after the transfer, the DNS settings must be prepared. You essentially have two strategies:
    • Retain existing name servers: If you use an external DNS service (e.g., Cloudflare) or plan to use the same web host as before, you can keep the existing NS records. All traffic will then continue to point to the same servers, and downtime will be minimal. You are only changing registrars, not DNS pointing.
    • Change name servers to the new registrar's/web host's: If you are also moving web hosts or wish to use the new registrar's DNS services, you must update the NS records. This is usually done after the domain has been transferred to the new registrar. Before the NS records are repointed, you must ensure that all A, MX, and other records are correctly configured with the new DNS service. A good practice is to manually copy all existing DNS records to the new platform before changing the NS records.
  6. Wait for propagation: When DNS settings are changed (especially NS records), it takes time for these changes to propagate across the internet. This is called DNS propagation and can take from a few minutes to 48 hours, although it is often quicker. During this period, some users will see the old website, while others will see the new one.

Example of DNS Migration with Minimal Downtime

Suppose you are transferring mycompany.com from Registrar A to Registrar B, and simultaneously moving the website from Web Host X to Web Host Y.

  1. Preparation at Web Host Y: You set up your website at Web Host Y and are assigned a temporary IP address, or you obtain the final IP address for the server.
  2. Update DNS records BEFORE transfer: Log in to Registrar A (or your current DNS manager) and change the A record for mycompany.com to point to the IP address at Web Host Y. Do the same for www.mycompany.com (if it's an A record or CNAME). Remember to also copy over all MX records and other important records. This is done while the domain is still with Registrar A.
  3. Wait for DNS propagation: Allow 2-24 hours for these A record changes to propagate. During this period, traffic will gradually start to point to the new web host.
  4. Execute domain transfer: Once you are confident that traffic is pointing correctly, you can initiate the actual domain transfer from Registrar A to Registrar B using the EPP code.
  5. Confirm DNS at Registrar B: Once the domain is with Registrar B, verify that the DNS settings are correct. Since you already pointed the A records to Web Host Y in step 2, and assuming you retain the same name servers (e.g., external name servers or Web Host Y's name servers), there will be minimal downtime. If you switch to Registrar B's own name servers, you must ensure all DNS records are configured there before repointing the NS records.

Common Mistakes and How to Avoid Them

  • Incomplete WHOIS information: Ensure that the contact information for the domain is up-to-date before a transfer. An outdated email address can prevent confirmation emails from reaching you.
  • Forgotten EPP code: Without this code, the process halts. Request it well in advance.
  • Incorrect DNS records: Carefully copy all existing DNS records. A missing MX record can lead to lost email, and an incorrect A record to the website not displaying.
  • Impatience with DNS propagation: Do not expect instantaneous changes. Plan for 24-48 hours of potential inconsistency.
  • Domain lock: Check that the domain is unlocked. A lock is a security feature that must be temporarily disabled.

Domain transfer and DNS configuration are technical processes that demand accuracy and understanding. By following these guidelines and prioritizing thorough preparation, you can ensure a seamless transition for your valuable digital assets. When in doubt, do not hesitate to consult an expert or your registrar.

Test yourself

Buy or sell a domain through us

Go to the brokerage service →