DNS records define how your domain connects to services such as websites and email.
Each record type has a specific purpose.

Incorrect DNS records can cause websites or email to stop working.

Where DNS Records Are Managed #

DNS records are managed using the DNS Zone Editor.

Changes:

• Apply after DNS propagation
• May take up to 24–48 hours to fully update

A Record Explained #

An A record points a domain to an IPv4 address.

Common uses:

• Connecting a domain to a web server
• Pointing a domain to a specific service

Example:

• example.com → 203.0.113.10

Most websites require at least one A record.

AAAA Record Explained #

An AAAA record points a domain to an IPv6 address.

It serves the same purpose as an A record, but for IPv6.

Example:

• example.com → 2001:db8::1

Some servers use both A and AAAA records.

MX Record Explained #

An MX record defines which mail servers receive email for your domain.

Important points:

• MX records are required for email hosting
• Priority values determine delivery order
• Incorrect MX records cause email delivery failure

Only mail servers listed in MX records will receive email.

TXT Record Explained #

A TXT record stores text-based information used for verification and security.

Common uses:

• SPF records for email authentication
• DKIM verification
• DMARC policies
• Domain ownership verification

TXT records are critical for email deliverability.

CNAME Record Explained #

A CNAME record points one domain name to another domain name.

Common uses:

• Redirecting subdomains
• Linking services without using IP addresses

Example:

• www.example.com → example.com

CNAME records cannot coexist with certain other record types on the same name.

Common DNS Mistakes #

• Creating duplicate records
• Mixing MX records from multiple providers
• Creating multiple SPF records
• Using incorrect IP addresses

These mistakes often cause service interruptions.

DNS Changes and Propagation #

After making DNS changes:

• Allow time for propagation
• Avoid repeated edits
• Test from multiple networks if needed

Propagation delays are normal.

Responsibility Notice #

You are responsible for:

• Creating correct DNS records
• Understanding record purpose
• Avoiding unsupported configurations

ProRedLine does not automatically correct DNS misconfigurations.