DNS record
DNS records: types, function, and usage
This article explains what DNS records are, which types exist, and how to configure them — for developers and system administrators working with Pixzo hosting or their own DNS infrastructure.
Requirements
- Access to the DNS management panel of your domain provider or Pixzo account - Basic knowledge of domain names and IP addresses - For verification: a terminal with `dig` (version 9.x or higher) or `nslookup` (version 9.x or higher)
What is a DNS record
A DNS record is a stored instruction within the Domain Name System (DNS) that links a domain name to specific data, such as an IP address. These instructions are located on DNS servers and are accessible to other servers and devices that want to resolve a domain name to a technical address. Without DNS records, you would have to visit every website via an IP address like `192.0.2.1` instead of `voorbeeld.nl`.
Steps: configuring a DNS record
Step 1: Determine which record type you need
Choose the right record type based on your goal:
- A record: links a domain name to an IPv4 address - AAAA record: links a domain name to an IPv6 address - CNAME record: points a domain name to another domain name - MX record: determines which mail server handles email for your domain - NS record: indicates which nameservers are authoritative for your domain - SOA record: contains zone information such as the responsible party and synchronization settings - TXT record: stores text data for verification, such as SPF, DKIM, or DMARC - PTR record: converts an IP address to a domain name (reverse DNS) - SRV record: points to network services, such as VoIP or instant messaging
Step 2: Log in to the DNS management panel
Go to your domain provider or Pixzo dashboard and open the DNS settings for the domain you want to manage. Look for the "DNS Records" or "Zone Editor" section.
Step 3: Add an A record
An A record is the most commonly used type and links your domain name to an IPv4 address. According to IBM, this is the standard use of an A record, defined in RFC 1035.
Type: A
Name: @ (or leave empty, depending on the provider)
Value: 192.0.2.1
TTL: 3600Step 4: Add a CNAME record for subdomains
A CNAME record acts as a redirect to a target domain, as DigiCert explains. Use this to point `www.voorbeeld.nl` to `voorbeeld.nl`, where an A record already exists. This prevents you from having to maintain multiple records with the same IP address.
Type: CNAME
Name: www
Value: voorbeeld.nl
TTL: 3600Step 5: Configure MX records for email
MX records determine which mail servers email for your domain should be sent to. You can set up multiple records with a priority — a primary and secondary mail server.
Type: MX
Name: @
Value: mail.voorbeeld.nl
Priority: 10
TTL: 3600Step 6: Set up TXT records for email verification
TXT records store text data that machines can read. Use them for SPF, DKIM, or DMARC — essential for email security. An SPF record looks like this:
Type: TXT
Name: @
Value: "v=spf1 include:_spf.voorbeeld.nl ~all"
TTL: 3600Step 7: Check NS and SOA records
NS records indicate which nameservers are authoritative for your domain. SOA records contain zone information: who is responsible, when the zone was last modified, and how often secondary nameservers synchronize. You normally do not configure these records manually — they are automatically managed by your DNS provider.
Step 8: Save changes and wait for propagation
Save all your changes. DNS changes spread across the network to other servers. The SOA record partly determines how quickly this happens. Propagation can take from a few minutes to 24 hours, depending on the TTL values.
Verification
Check whether your DNS records are correctly configured using `dig`:
Check an A record
dig voorbeeld.nl A +short</p><p>Check an MX record
dig voorbeeld.nl MX +short</p><p>Check a TXT record
dig voorbeeld.nl TXT +short</p><p>Check a CNAME record
dig www.voorbeeld.nl CNAME +shortThe output shows the values you have set. If you see nothing, wait a few minutes and try again — DNS caching can cause delays.
Common problems
Problem: DNS changes are not visible
Solution: wait until the TTL has expired. Lower the TTL value before making changes if you want to test quickly. Also verify that you are making changes with the correct DNS provider — some domains use external nameservers.
Problem: Email is not arriving after an MX change
Solution: check that your MX record contains a valid hostname, not an IP address. MX records must point to a hostname that itself has an A record. Also verify the priority — lower values take precedence.
Problem: CNAME record does not work for the root domain
Solution: CNAME records cannot exist alongside other records at the same level. For the root domain (`example.nl`), always use an A record. CNAME is only suitable for subdomains such as `www.example.nl`.
Record types and their function
The different record types are defined in RFC 1035, the technical standard that lays the foundation for the DNS protocol. Each type has a specific role, and they work together to make the domain name system functional.
The AAAA record is the IPv6 equivalent of the A record and links a domain name to an IPv6 address. Although this type is not explicitly mentioned in RFC 1035, it follows logically from the pattern of A records and is widely recognized as standard.
PTR records are used for reverse DNS: converting an IP address to a domain name. DigiCert describes this as the reverse of A and AAAA records. These records are important for logging, troubleshooting, and security — for example, to verify whether an IP address actually belongs to a trusted server.
SRV records indicate where network services such as instant messaging or VoIP can be found. They fall under the list of commonly used types according to IBM, but are configured manually less often than A or MX records.
The Dutch explanation on CloudGeek describes DNS records as stored instructions on the DNS server — the functional basis of every domain on the internet. The combination of these record types ensures that users work with readable domain names while computers and networks use technical addresses. Standardization via RFC 1035 guarantees consistency and interoperability between different DNS implementations worldwide — a property that remains crucial as the number of domains and the complexity of network services continue to grow.