For a domain to function correctly, several DNS records need to be configured behind the scenes. These records determine which IP address your domain points to, where your emails are delivered, and how you verify ownership of your domain with various services.
An A record maps a domain name directly to an IPv4 address. When someone types example.com into a browser, this record tells them which server IP address to connect to. It is the most fundamental record for making a website visible.
An MX (Mail Exchanger) record defines which mail server should receive email sent to your domain. You can define multiple MX records, and mail servers are attempted in order of priority, with lower values tried first.
A CNAME record points one subdomain to another domain or subdomain name rather than an IP address. For example, if you want www.example.com to point to example.com, a CNAME record handles that redirection.
A TXT record stores text-based information for a domain. Common uses include email authentication records like SPF and DKIM, as well as verification codes required by third-party services to confirm domain ownership.
Wherever your domain's nameservers point is typically where you manage its DNS records. Just like nameserver changes, updates to DNS records can take a few hours to propagate fully across the internet.
Configuring DNS records correctly is essential for everything from website accessibility to reliable email delivery. It is a good practice to back up your existing records before making any changes.
An A record points a domain name directly to an IP address, while a CNAME record points a domain name to another domain name as an alias.
An MX (Mail Exchange) record determines which server receives the emails sent to a domain. If it is not configured correctly, your emails will not be delivered.
A TXT record is a text-based DNS record that is generally used for domain verification, email security settings such as SPF and DKIM, and site ownership verification.
Depending on the TTL (Time To Live) value, changes to DNS records usually propagate worldwide within a few minutes to 24-48 hours.