Configuring DNS Resource Records in Your Control Panel: A Complete Guide

DNS resource records (RRs) are the fundamental building blocks of the Domain Name System — the global infrastructure that translates human-readable domain names into machine-readable addresses. Whether you're launching a new website, setting up business email, or verifying domain ownership with a third-party service, understanding how to configure resource records in your DNS control panel is an indispensable skill for any website owner, developer, or systems administrator.

This comprehensive guide walks you through every major DNS record type, explains exactly how each one works, and provides step-by-step instructions for adding and verifying them correctly.

What Are DNS Resource Records?

A DNS resource record is a structured data entry stored in a DNS zone file. Each record contains specific information that tells the internet how to handle requests related to your domain — where to route web traffic, which server handles your email, and what text-based metadata is associated with your domain.

Every resource record consists of several core fields:

• Name – The domain or subdomain the record applies to
• Type – The category of record (A, AAAA, CNAME, MX, TXT, etc.)
• Value/Data – The actual information the record contains
• TTL (Time to Live) – How long (in seconds) DNS resolvers should cache the record before re-querying

Misconfigured DNS records are one of the most common causes of website downtime, email delivery failures, and failed domain verifications. Getting them right from the start saves significant troubleshooting time later.

Common DNS Record Types Explained

Before diving into configuration steps, it's worth understanding what each record type does and when you'll need it.

A Record

Maps a domain or subdomain to an IPv4 address. This is the most fundamental DNS record — it's what allows browsers to find your web server when someone types your domain name.

Example: example.com → 192.0.2.1

AAAA Record

Maps a domain or subdomain to an IPv6 address. As IPv6 adoption grows, having an AAAA record alongside your A record ensures your site is accessible over both protocols.

Example: example.com → 2001:db8::1

CNAME Record

A Canonical Name record creates an alias from one domain name to another. Instead of pointing to an IP address, a CNAME points to another hostname. This is commonly used for www subdomains, CDN configurations, and third-party service integrations.

Important: You cannot use a CNAME record on the root (apex) domain alongside other records. Use it only on subdomains.

Example: www.example.com → example.com

MX Record

A Mail Exchange record specifies which mail server is responsible for receiving email on behalf of your domain. MX records include a priority value — lower numbers indicate higher priority. You can configure multiple MX records for redundancy.

Example: example.com → mail.example.com (Priority: 10)

TXT Record

A Text record stores arbitrary text data associated with your domain. TXT records are widely used for:

• SPF (Sender Policy Framework) – Defines which servers are authorized to send email from your domain
• DKIM (DomainKeys Identified Mail) – Stores the public key used to verify email signatures
• DMARC – Sets policies for handling emails that fail SPF/DKIM checks
• Domain verification – Used by Google Search Console, Microsoft 365, and other services to confirm domain ownership

NS Record

Name Server records specify which DNS servers are authoritative for your domain. These are typically set at your domain registrar and point to your hosting provider's nameservers.

PTR Record

A Pointer record performs reverse DNS lookups — mapping an IP address back to a hostname. PTR records are particularly important for mail server reputation and are usually configured at the server level.

Accessing Your DNS Control Panel

To manage resource records, you need access to the DNS management interface provided by your domain registrar or hosting provider. The exact interface varies by provider, but the process is broadly the same.

Step 1: Log in to your account at your domain registrar or hosting provider's dashboard.

Step 2: Navigate to the DNS Management, DNS Settings, or Zone Editor section. This is sometimes found under "Domain Management" or "Advanced Settings."

Step 3: Select the domain you want to configure.

> Pro tip: If your domain is registered with one provider but hosted with another (such as AlexHost VPS Hosting), you'll need to either update your domain's nameservers to point to your hosting provider, or log in to your registrar's DNS panel and manually add the records provided by your host.

Step-by-Step: Configuring Common Resource Records

3.1 Adding an A Record

An A record is typically the first record you'll configure when pointing a domain to a web server.

1. In your DNS control panel, locate the A Records section and click Add Record.
2. Fill in the following fields:

• Host/Name: Enter @ to point the root domain (e.g., example.com), or enter a subdomain like www or blog.
• Points To / Value: Enter the IPv4 address of your server (e.g., 192.0.2.1).
• TTL: Leave at the default value (typically 3600 seconds / 1 hour) unless you have a specific reason to change it. Use a lower TTL (e.g., 300) if you anticipate making frequent changes.

1. Click Save or Add Record.

Common use case: If you're running a website on a VPS or Dedicated Server, you'll add an A record pointing your domain to your server's public IP address.

3.2 Adding an AAAA Record

The process is identical to adding an A record, but you select AAAA as the record type and enter an IPv6 address in the value field.

1. Select AAAA as the record type.
2. Enter the Host/Name (e.g., @ or www).
3. Enter the IPv6 address (e.g., 2001:db8::1).
4. Set the TTL and save.

3.3 Adding a CNAME Record

CNAME records are useful for aliasing subdomains or integrating third-party services.

1. Locate the CNAME Records section and click Add Record.
2. Fill in the fields:

• Host/Name: Enter the subdomain you want to alias (e.g., www, shop, blog).
• Points To / Value: Enter the target hostname (e.g., example.com or myshop.shopify.com).
• TTL: Set as appropriate (default 3600 is fine for most cases).

1. Click Save.

> Note: Never create a CNAME record for your root domain (@). If you need to alias the root domain, use an ALIAS or ANAME record if your DNS provider supports it, or use an A record pointing to the target's IP address.

3.4 Adding an MX Record

Correct MX record configuration is critical for reliable email delivery. If you're using AlexHost Email Hosting or a third-party email provider, they will supply the exact MX record values you need.

1. Locate the MX Records section and click Add Record.
2. Fill in the fields:

• Host/Name: Enter @ (representing the root domain) or leave blank, depending on your panel.
• Mail Server / Value: Enter the hostname of your mail server (e.g., mail.example.com or aspmx.l.google.com for Google Workspace).
• Priority: Enter a numeric priority value. Lower numbers = higher priority. A single mail server typically uses 10. For backup servers, use 20 or 30.
• TTL: Default 3600 is standard.

1. Click Save.

Multiple MX records: For redundancy, add a primary server at priority 10 and a backup server at priority 20. If the primary server is unreachable, email will automatically route to the backup.

3.5 Adding a TXT Record

TXT records are essential for email authentication and domain verification workflows.

1. Locate the TXT Records section and click Add Record.
2. Fill in the fields:

• Host/Name: Enter @ for the root domain, or a specific subdomain if required (e.g., _dmarc for DMARC records).
• Value / Text: Paste the exact text string provided by your email provider or verification service. Examples:
• SPF: v=spf1 include:_spf.example.com ~all
• Google verification: google-site-verification=xxxxxxxxxxxxxxxx
• DMARC: v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com
• TTL: Default 3600 is appropriate.

1. Click Save.

> Important: You can have multiple TXT records on the same hostname, but you should only have one SPF record per hostname. If you need to authorize multiple senders, combine them into a single SPF record rather than creating separate ones.

Understanding TTL Values

TTL (Time to Live) controls how long DNS resolvers cache your record before checking for updates. Choosing the right TTL depends on your situation:

Best practice: If you're planning a server migration or DNS change, lower your TTL to 300 at least 24–48 hours in advance. This reduces the propagation window when you make the actual change. After the migration is complete, raise the TTL back to 3600 or higher.

DNS Propagation: What to Expect

After saving any DNS change, it doesn't take effect instantly worldwide. DNS propagation — the process of updated records spreading across global DNS resolvers — typically takes between a few minutes and 48 hours, depending on:

• The previous TTL value of the record
• Your DNS provider's update frequency
• The caching behavior of individual ISPs and resolvers

During propagation, some users may see the old DNS values while others see the new ones. This is normal and expected behavior.

Verifying Your DNS Records

After making changes, always verify that your records are configured correctly and have propagated as expected.

Online DNS Lookup Tools

These web-based tools let you check DNS records from multiple global locations simultaneously:

• DNS Checker – Checks propagation across dozens of global DNS servers
• MXToolbox – Excellent for verifying MX records and diagnosing email delivery issues
• WhatsMyDNS – Simple, visual propagation checker for all record types

Command-Line Tools

For more granular control, use terminal commands directly:

Check an A record:

dig example.com A

Check MX records:

dig example.com MX

Check TXT records (e.g., SPF):

dig example.com TXT

Using nslookup (cross-platform):

nslookup example.com
nslookup -type=MX example.com
nslookup -type=TXT example.com

Query a specific DNS server (useful for checking if your registrar's nameservers have updated):

dig @8.8.8.8 example.com A

DNS Configuration Best Practices

Following these best practices will help you avoid common pitfalls and maintain a healthy DNS configuration:

1. Document your DNS records. Keep a spreadsheet or notes file with all your current DNS records, their values, and the reason each one exists. This is invaluable during troubleshooting or migrations.

1. Don't delete records before verifying replacements. When updating a record, add the new record first, verify it's working, then remove the old one.

1. Use a reliable DNS provider. Your DNS provider's uptime and performance directly affect your website's availability. Hosting your site on a platform like AlexHost Shared Hosting or a VPS with cPanel gives you access to robust, managed DNS infrastructure.

1. Secure your domain with an SSL certificate. DNS configuration and SSL go hand in hand — once your A records are pointing correctly, make sure your site is secured with an SSL Certificate to protect user data and improve search rankings.

1. Register and manage your domain in one place. Using AlexHost Domain Registration alongside your hosting simplifies DNS management by keeping everything under one dashboard.

1. Monitor DNS health regularly. Set up monitoring alerts for DNS failures or unexpected record changes, especially for business-critical domains.

1. Be cautious with wildcard records. A wildcard A record (*.example.com) routes all subdomains to a single IP, which can be convenient but may cause unintended routing if not carefully managed.

Troubleshooting Common DNS Issues

Conclusion

Configuring DNS resource records correctly is one of the most impactful things you can do for the reliability and performance of your online presence. A records connect your domain to your server, MX records ensure your email reaches its destination, TXT records authenticate your identity and protect against spam, and CNAME records give you the flexibility to alias and integrate services seamlessly.

The key takeaways from this guide:

• Understand each record type before adding it — knowing what a record does prevents costly mistakes
• Use appropriate TTL values based on how frequently you expect to make changes
• Always verify changes using both online tools and command-line utilities
• Plan DNS changes in advance, especially for production environments with real users

Whether you're managing a personal blog, a business website, or a complex multi-server infrastructure, mastering DNS configuration gives you direct control over how your domain behaves on the internet. Pair that knowledge with a reliable hosting provider and a well-structured server environment, and you'll have a rock-solid foundation for everything you build online.