DNS Record Settings: A Practical Guide to Safely Managing Your Domain

DNS Record Settings: A Practical Guide to Safely Editing Your Domain

Log in to your domain or DNS manager and export the existing zone before changing anything. Then edit the target record — A, CNAME, or MX — depending on what you want to achieve. A change takes anywhere from a few minutes to 24 hours to propagate across all servers worldwide, and in rare cases up to 72 hours. If your site or email still isn't working after that time, check the record with a diagnostic tool before calling support.

In short:

• If you want to change your DNS, export the existing zone and carefully edit the A, CNAME, or MX records, since an incorrect setting can cause long-term problems.
• Propagation of changes usually takes anywhere from a few minutes to 24 hours, and in rare cases up to 72 hours, so it's important to monitor the status with tools like nslookup, dig, or online checkers.
• Before making major changes, lower the TTL to the minimum value to speed up propagation, and always make a backup of the zone so you can quickly revert if something goes wrong.
• DNS editing for complex migrations — including enabling DNSSEC or configuring email protection with SPF, DKIM, and DMARC — should be handled by experienced professionals, to avoid losing business email or making your site unreachable.
• For less demanding tasks, we recommend using a service like Moxy Web, which provides secure and professional management of DNS records and configuration of security mechanisms.

Table of Contents

• What a DNS zone is and what types of records exist
• How to edit DNS records in cPanel, at your registrar, and on FreeDNS
• Practical examples of records for the web, DNS, and email
• How long propagation takes and how to check a change
• Security when editing: backup, DNSSEC, and email protection
• Quick troubleshooting checklist and tools
• Checklist before making a change, and when to call an expert
• Why it pays to slow down when editing DNS
• When to leave DNS to Moxy Web
• Sources
• Frequently asked questions

What a DNS zone is and what types of records exist

A DNS zone is a collection of all the records for a single domain, stored on authoritative name servers. Every zone also contains an SOA record (Start of Authority), which defines basic information about the zone, such as the serial number and timing parameters for syncing between servers.

For day-to-day management, you'll mainly encounter the following record types:

• A – links a domain name to an IPv4 address (for example, 91.185.203.12).
• AAAA – same as A, but points to an IPv6 address.
• CNAME – redirects one name to another domain name (for example, www to the bare domain).
• MX – specifies which server receives email for the domain, and with what priority.
• NS – indicates which name servers are authoritative for the domain.
• TXT – stores arbitrary text content, most often used for ownership verification or SPF.
• SRV – routes specific services (such as VoIP) to a particular server and port.
• CAA – specifies which certificate authorities are allowed to issue an SSL certificate for the domain.

Every record also has a TTL (Time To Live) value, which tells servers around the world how long to "remember" the old data. A lower TTL means the change becomes visible faster; a higher TTL means less load on DNS servers.

How to edit DNS records in cPanel, at your registrar, and on FreeDNS

Before touching anything, export the zone or at least take a screenshot of the current settings. This lets you quickly revert to the previous configuration if something goes wrong.

The process in cPanel is fairly straightforward:

1. Log in to cPanel and find the Zone Editor tool (some providers call it the DNS Zone Editor).
2. Select the domain whose records you want to edit.
3. Click Add Record for a new record, or Edit next to an existing one, and enter the name, type, and value.
4. Save the change — this process is standard for most hosting providers that use cPanel.

If your domain is managed by a registrar without cPanel, look for a "DNS records" or "domain management" section in your account — the interface is functionally similar, just with different button layouts. On FreeDNS, you first need to select the domain from the list, then open the zone editing section and add or change the record there.

The most common mistake is combining an A record and a CNAME record on the same name. If your provider requires a CNAME for a subdomain, no other record may exist under that same name, otherwise you get a conflict that the system either rejects or misinterprets.

Pro tip: For the domain name without a prefix (the bare domain, i.e. "@"), almost always use an A record, and for www use a CNAME pointing to the bare domain. The reverse combination often causes errors with some providers.

Practical examples of records for the web, DNS, and email

Concrete examples help more than theory. Below are sample values you'll most likely need when setting up your own domain.

• A record for the main site: name @ (or a blank field, depending on the interface), value the server's IP address, for example 91.185.203.12.
• CNAME for www: name www, value vasadomena.si (pointing back to the bare domain).
• CNAME for a subdomain: name shop, value the address specified by your store provider, for example shop.ponudnik.com.
• MX record: name @, value the mail server address (for example mail.vasadomena.si), priority often 10 for the primary server and 20 for the backup.
• TXT record for SPF: value something like v=spf1 include:_spf.ponudnik.com ~all, which specifies which servers are allowed to send mail on your behalf.

DKIM adds a digital signature to every outgoing message, while DMARC determines what happens to mail that fails SPF or DKIM checks. Without all three of these records together, email often ends up in the spam folder, even if the content is completely legitimate. A detailed overview of SPF, DKIM, and DMARC configuration is available in this email protection guide, which also explains common causes of blocking.

How long propagation takes and how to check a change

A DNS record change is usually visible within a few minutes, sometimes takes up to 24 hours, and in rare cases up to 72 hours to propagate across all caches worldwide. The reason is the TTL value of the previous record, which servers honor until it expires.

Checking isn't complicated — you just need the right tool:

• The command nslookup vasadomena.si shows the current A record as seen by your computer.
• The command dig vasadomena.si MX displays all MX records and their priority.
• The command dig vasadomena.si TXT reveals SPF and other text records.
• Zonemaster performs a comprehensive delegation diagnosis and flags mismatches between the registrar and the authoritative servers.
• Online checkers (like whatsmydns.net) show the record's status across multiple locations at once.

Security when editing: backup, DNSSEC, and email protection

Every DNS record change should start with a zone export, or at least a screenshot of the existing values. This step drastically speeds up recovery if something breaks after the change, since you have an exact record of what to revert to.

DNSSEC adds digital signatures to your DNS records and prevents certain types of attacks where an attacker redirects traffic to the wrong server. Enabling it requires support from both your registrar and hosting provider, so check that both offer it before activating the feature. A misconfigured DNSSEC setup can make a domain unreachable, so caution matters just as much here as when enabling it.

SPF, DKIM, and DMARC together protect the deliverability of your business email and prevent someone else from sending mail on your behalf.

Pro tip: A few days before a major change, lower the TTL to 300 seconds (5 minutes), make the change, verify it works, then raise the TTL back to a higher value, such as 3,600 seconds, for stability.

Quick troubleshooting checklist and tools

When your site or email stops working after a change, follow this sequence:

1. Check whether the cause is an incorrect A record (pointing to the old IP), a missing MX record, or a conflict between an A and CNAME record on the same name.
2. Correct the record to the right value and save the change.
3. Use nslookup and dig to check whether the change is already visible on your network.
4. Use Zonemaster or an online checker to review the status across multiple global locations at once.
5. If the record still shows the old value everywhere after 24 hours, it's most likely due to too high a TTL or an error at the registrar — this is the point to seek professional help.

Checklist before making a change, and when to call an expert

Before every change, export the zone, lower the TTL, and make sure you understand the exact purpose of each record. For complex hosting migrations, enabling DNSSEC, or critical business email, we recommend having an experienced partner carry out the change, since a mistake here can mean lost sales or lost customer messages. The author of this guide, Ziga, regularly advises companies on exactly these kinds of transitions at Moxy Web.

Why it pays to slow down when editing DNS

The biggest mistake I see when people edit DNS records isn't technical — it's rushing. People change a record, skip backing up the zone, and then wonder half an hour later, when something goes wrong, why they can't find their way back. Conventional advice often skips exactly this step, because it focuses on "how to add a record" rather than "how to safely get back if I make a mistake."

Another underrated factor is TTL. Most people set it once and never look at it again, even though TTL is exactly what determines whether propagation takes five minutes or an entire day. Anyone who plans a change in advance and lowers the TTL a few days beforehand saves themselves the nervous waiting and repeated checking with nslookup.

The most underrated part of the whole story, though, is email security. Companies build a beautiful website and then forget about SPF, DKIM, and DMARC, so their mail ends up in customers' spam folders. Technically the site works perfectly, but the business loss can be significant. The priority should be the other way around: secure the email first, then worry about making the site look nice.

— Ziga

When to leave DNS to Moxy Web

If reading about the Zone Editor, TTL, and SPF records has worn you out, you already know why it's better to leave this service in experienced hands. For companies building their digital presence, we can handle DNS record management, review the zone before making changes, and set up SPF, DKIM, and DMARC for reliable business email. The basic service can include a review of the domain's current state, a safe implementation of the change with a zone export as a safety net, and support enabling DNSSEC where it makes sense. Instead of risking website downtime or lost mail during a hosting migration, you can leave this step to experienced professionals. Visit Moxy Web to see how we can ensure a safe transition for your domain, or send an inquiry for a specific proposal tailored to your situation.

Sources

• Support — changing DNS for a .SI domain
• Domenca — Editing DNS records on a cPanel server

Frequently asked questions

What happens if I forget to back up the zone?

Without a zone export or a screenshot of the settings, if something goes wrong you'll have to manually reconstruct every record from memory, which extends the downtime and increases the risk of mistakes.

How long does a DNS record change take?

The change becomes visible anywhere from a few minutes to 24 hours, and in rare cases up to 72 hours, depending on the TTL value of the previous record.

How do I check whether a DNS record is already active?

Use the nslookup or dig command for a quick check on your own network, and Zonemaster or an online checker for a comprehensive diagnosis.

Do I need SPF, DKIM, and DMARC if I only have one business email address?

Yes — without these three records, even legitimate mail can often end up in the recipient's spam folder, regardless of the size of your business.

When should an expert make DNS changes instead of me?

For complex hosting migrations, enabling DNSSEC, or critical business email, it's worth leaving the setup to an experienced partner like Moxy Web, since a mistake here means serious business disruption.

Recommended

• Domain Registration Guide: Step by Step
• How to Choose the Right Domain for Your Business
• How to Set Up Secure Website Hosting
• Guide to a Secure Business Website