The DNS (Domain Name System) is the internet’s phone book: it translates the domain name (for example, cegnev.hu) into the IP address where the website is hosted, and it tells email systems where to deliver emails sent to the @cegnev.hu address. If a DNS record is incorrect, the website won’t load, emails won’t arrive, or they’ll end up in the spam folder, so it’s worth understanding what each one is for.

In this guide, we explain how DNS resolution works, what the most common record types are used for, where and how you can edit them, what TTL and propagation are, and what to look out for to ensure that a change does not cause downtime.

How does domain name resolution work?

When someone types the address cegnev.hu into their browser:

1. The machine first looks for the answer in its own cache, then in the Internet service provider’s (or a configured one, such as 1.1.1.1) recursive name server.
2. If it isn’t there, the recursive name server queries the root servers to find out who is responsible for the .hu extension, and then queries the .hu name server to find out who is responsible for cegnev.hu-ért.
3. The .hu name server provides the domain’s authorised name servers (these are the NS records you specified when registering the domain).
4. The authoritative name server returns the requested record from the domain’s DNS zone, such as the IP address of the A record.
5. The response is cached for the duration of the TTL value, so the next request does not need to go through the whole process again.

It is important to distinguish between two things:

• Name servers (NS) specify the location of the domain’s zone. You configure these via your domain registrar.
• DNS records are entries within a zone that you edit at the location where the zone is managed (for example, via the hosting control panel).

If the name servers point to your hosting account, you’ll need to edit the records via your hosting control panel; if they point elsewhere (such as Cloudflare), then you’ll need to do so there. A common mistake is for someone to edit a record on the hosting platform whilst the domain’s name servers are pointing elsewhere, meaning the change has no effect. Our article on the A-record versus name server change discusses how to choose between the two approaches, whilst our separate guide covers how to change name servers securely.

The most common record types

Record	What is it for?	Example
A	Domain name → IPv4 address	cegnev.hu → 203.0.113.10
AAAA	Domain name → IPv6 address	cegnev.hu → 2001:db8::10
CNAME	Alias for another name	www.cegnev.hu → cegnev.hu
MX	Where should letters be delivered, as a priority?	10 mail.cegnev.hu
TXT	Text data: SPF, DKIM, DMARC, proof of ownership	v=spf1 ... ~all
CAA	Which certification authorities can issue SSL certificates?	0 issue "letsencrypt.org"
NS	The name servers managing the zone	ns1.szolgaltato.hu
SRV	Location and port of services (e.g. Microsoft 365, SIP)	_sip._tcp ...
PTR	IP address → name (reverse lookup)	The owner of the server’s IP address configures it

A detailed description of record types can be found in the article on DNS record types.

A and AAAA

The basis for your website’s accessibility. The A record specifies the domain’s IPv4 address, whilst the AAAA record specifies its IPv6 address. If your server also supports IPv6, it is worth setting up both, but only if the IPv6 address is actually working: a faulty AAAA record will prevent visitors using IPv6 from accessing the site.

CNAME

It redirects one name to another, for example www.cegnev.hu to cegnev.hu, or a subdomain to an external service (online shop platform, email service provider). Two rules: you cannot set a CNAME record for the domain root (cegnev.hu), and a name that has a CNAME record cannot have any other records associated with it.

MX

This tells you which server receives your domain’s emails. There may be several MX records; the one with the lowest priority number is the primary one, whilst the others are backups. If you move your email to another provider (for example, to a separate email hosting service or Microsoft 365), you will need to update the MX record. The steps for doing this in cPanel are described in the article on modifying MX records.

TXT: SPF, DKIM, DMARC

Email authentication is carried out via TXT records:

• SPF (v=spf1 ...): which servers are authorised to send emails on behalf of the domain. A domain can only have one SPF record; if multiple services send emails on your behalf, they must all be listed in a single record. SPF may use up to 10 additional DNS queries (include, a, mx).
• DKIM (selector._domainkey.cegnev.hu): the public key for digitally signing emails.
• DMARC (_dmarc.cegnev.hu): what should the receiving server do with emails that fail authentication, and where should it send a report?

Google, Yahoo and Microsoft now require all three from major senders, and emails without authentication are increasingly ending up in the spam folder. Our guide covers how to set up DKIM, SPF and DMARC.

You can also use TXT records to verify domain ownership with Google Search Console, Microsoft 365 or other services.

CAA

This specifies which certification authorities are permitted to issue SSL certificates for your domain. If there is no CAA record, any provider can issue a certificate; if there is one, only those listed can do so. When configuring this, don’t forget to include the provider that automatically issues certificates for your hosting (such as Let’s Encrypt), otherwise certificate renewal will be blocked. Our knowledge base article explains what a CAA record is and how to set it up.

Video: DNS Records Explained (PowerCert Animated Videos)

TTL and propagation

The TTL (time to live) specifies, in seconds, how long caches may store the record. A TTL of 3600 means that, following a change, the old value may still be served for up to one hour.

• For stable records, a TTL of 1–4 hours (3600–14400) is a good choice.
• Before any planned changes (for example, a day or two before a server migration), reduce the TTL to 300 seconds so that the change propagates quickly, and then reset it after the migration.

Propagation is the time it takes for a change to take effect everywhere. When modifying a record, this depends on the old TTL and typically takes anywhere from a few minutes to a few hours. Changing name servers takes longer because the registries’ caches are also affected: this can take up to 24–48 hours. You can speed up the process on your own computer by flushing the local cache; the steps for doing this are described in the article on clearing the local DNS cache. You can read more about DNS propagation and how long it takes in a separate article.

Editing DNS records in cPanel

If your domain name servers point to your aWh cPanel hosting account:

1. Log in to cPanel and open the Zone Editor menu item.
2. Next to the domain, select the ‘Manage’ option.
3. New record: use the ‘Add Record’ button to enter the name, TTL, type and value.
4. To make changes: use the ‘Edit’ button next to the existing record.
5. Once saved, the change will take effect once the TTL has expired.

The cPanel Email Deliverability menu is the most convenient way to set up SPF and DKIM: it shows you what’s missing and fixes it with a single click.

Subdomain: the subdomain (for example, shop.cegnev.hu) in the zone is a simple A or CNAME record. If you also want to host a website on it, add it via the ‘Domains’ menu in cPanel, and cPanel will automatically create the necessary record. This is covered in the article on adding domains and subdomains in cPanel.

External platform: if the website runs on an external service (such as Shopify or Wix), the service provider will specify which A and CNAME records need to be set up; typically, an A record for the root and a CNAME for www.

Verification

• From the command line: dig cegnev.hu A, dig cegnev.hu MX, dig TXT _dmarc.cegnev.hu (on Linux and macOS), or nslookup -type=MX cegnev.hu (on Windows). The command dig @8.8.8.8 ... queries a specific name server.
• Using online tools: the DNS Checker or WhatsMyDNS show how the record is viewed by different name servers around the world; MXToolbox checks the email records.
• After making changes, check that the website loads, that emails are coming through, and that HTTPS is working.

Common errors

• You’re making changes in the wrong place: the domain’s name servers point to a different location from where you’re editing the zone.
• Two SPF records: the SPF will be invalid, and emails may end up in the spam folder. Merge them into one.
• Forgotten MX or TXT records during migration: if you change your name servers, you must also transfer the mail and verification records to the new zone, not just the A record.
• Missing full stop at the end: on some platforms, a full stop is required at the end of the full name (mail.cegnev.hu.), otherwise the system will append the domain (mail.cegnev.hu.cegnev.hu).
• Incorrect AAAA record: due to a non-functioning IPv6 address, some visitors are unable to access the site.
• TTL set too high before migration: the switch takes hours or days.
• CAA record without a certificate authority: automatic SSL will not be renewed.

If you’ve made a mistake: revert to the previous value. It’s worth making a backup of the entire zone before making any changes (by exporting the zone in cPanel or taking a screenshot). The issue will persist for as long as the record’s TTL; if you’re unsure what the correct value was, please contact us.

DNSSEC

DNSSEC protects DNS responses with a digital signature, preventing attackers from returning a false response to a query. To enable it, you need both a nameserver that signs the zone and a DS record set up with the registrar. It is a useful form of protection, but if configured incorrectly, the domain may become completely inaccessible, so always check before changing your name servers. Our article introducing DNSSEC and our article on problems caused by DNSSEC cover this topic.

Summary

DNS records determine where your website points to and where your emails are delivered. Know where your zone is (the name servers will tell you), understand the main record types (A, AAAA, CNAME, MX, TXT, CAA), reduce the TTL before making any planned changes, and always check the result after making changes. SPF, DKIM and DMARC are now essential for email.

Frequently Asked Questions

How long does it take for DNS records to update?

A record change typically takes effect within a few minutes to a few hours once the old TTL has expired. Replacing the name servers may take up to 24–48 hours.

Can I change my DNS settings if my domain isn’t hosted with aWh?

Yes. If your domain’s name servers point to your aWh hosting account, you can edit the records via the hosting control panel, regardless of where the domain is registered. If the name servers are hosted elsewhere, you’ll need to make the changes there.

What happens if I accidentally delete the A record?

The website will become inaccessible once the TTL expires. Restore it using the previous IP address; the fix will take effect in the same way, depending on the TTL.

How many MX records can I have?

What’s more: the one with the lower priority number is the primary one, and the others are backups. Only specify servers that actually host the domain’s subdomains.

What is the recommended TTL?

Stable records range from 3,600 to 14,400 seconds; temporarily 300 seconds prior to a migration or planned change.

What is the difference between a name server and a DNS record?

The name server (NS) specifies which server manages the domain’s zone; the DNS records are the entries within the zone (A, MX, TXT, etc.) that contain the actual addresses and settings.

Do I need an AAAA record if I already have an A record?

It’s not compulsory, but if your server has a working IPv6 address, it’s worth setting it up. However, you should avoid adding an incorrect AAAA record.

Do you need a DNS record for an SSL certificate?

To obtain the free, automatic certificate, all you need to do is ensure that the domain’s A record points to the hosting service. For some certificates (such as wildcard certificates), you will need to add a temporary TXT or CNAME record for verification; if you use a CAA record, the certificate issuer must be listed in it.

• dns
• guides
• for beginners
• cpanel