---
title: DNS Records
description: DNS instruction rows (A, AAAA, CNAME, MX, TXT, …) that point names to IPs, mail, and verification services.
canonical: https://penasihathosting.com/en/hosting-wiki/dns-records
type: wiki
locale: en
updated: 2026-07-15
author: Willya Randika
---

# DNS Records

## Overview

- **Summary:** DNS instruction rows (A, AAAA, CNAME, MX, TXT, …) that point names to IPs, mail, and verification services.
- **Author:** Willya Randika ([profile](/penulis/willya-randika))

## Article

**DNS records** are the rows in a [DNS](/en/hosting-wiki/dns-domain-name-system) zone that tell the internet what to do with a name: which IP, which mail server, or which verification string. Together they are the domain’s address book.

You edit them in the DNS panel controlled by the domain’s [nameservers](/en/hosting-wiki/nameserver). Editing the wrong panel (a non-authoritative zone) is the most common reason a “change” never goes live.

## Records You Will Use Most

| Type | Practical job |
| --- | --- |
| **A** | Name → [IPv4](/en/hosting-wiki/ip-address) |
| **AAAA** | Name → IPv6 |
| **CNAME** | Alias to another name (not a raw IP) |
| **MX** | Mail delivery target |
| **TXT** | Free text: SPF, DKIM, Google verifies, etc. |
| **NS** | Authoritative nameservers (change carefully) |
| **CAA** | Which CAs may issue certificates |

Not every record is required. A simple site often needs an A record (or the host’s documented CNAME pattern) plus MX/TXT if you use domain email.

## A Simple Pattern

1. Apex A → hosting IP  
2. `www` CNAME → apex (or its own A)  
3. MX → mail provider  
4. TXT → SPF/DKIM so [SMTP](/en/hosting-wiki/smtp) is less spammy  

One wrong record does not always break everything — but a bad MX can kill email while the website still loads. Migration checklists should treat “web” and “mail” as separate tracks.

## TTL and Propagation

Each record has a [TTL](/en/hosting-wiki/dns-ttl). High values cache longer; low values make changes visible sooner. Before a major cutover, lower TTL first, then change A/MX. How that spreads worldwide is covered in [domain propagation](/en/hosting-wiki/domain-propagation).

## What to Watch For

- Edit the **active** zone (matching live nameservers)  
- Respect TTL — changes are not always instant  
- Do not delete verification TXT records you still need  
- Apex CNAMEs are restricted on many classic DNS setups; follow your provider’s pattern  
- Verify with [DNS Lookup](/en/tools/dns-lookup), ideally from more than one network  

## FAQ

<Accordion>
  <AccordionItem title="How long until a new record works?">
    Minutes to many hours depending on TTL and resolver caches. MX mistakes feel painful quickly because mail fails.
  </AccordionItem>
  <AccordionItem title="Can I have multiple A records?">
    Yes for simple multi-IP setups, but it must be intentional. Accidental duplicates create confusing behavior.
  </AccordionItem>
  <AccordionItem title="My TXT value is very long — is that OK?">
    There are per-string length limits; long SPF/DKIM values are often split. Use the exact format your mail provider gives you.
  </AccordionItem>
  <AccordionItem title="Should I edit NS records inside the zone?">
    Rarely, unless you understand the impact. Registrar nameservers and zone NS records need to stay consistent.
  </AccordionItem>
</Accordion>