🗂️

DNS Resource Records Summary

Nov 10, 2025

Overview

  • The transcript explains common DNS resource record types, their purposes, and how they appear in DNS configurations.
  • Examples illustrate A/AAAA, CNAME, MX, TXT (SPF, DKIM), NS, SOA, and PTR records.

DNS Resource Records Overview

  • Resource records store DNS data: names, IPs, mail handling, aliases, verification details.
  • DNS queries use these records to resolve names, verify senders, and locate services.

Start of Authority (SOA)

  • Defines zone details: domain, serial number, retry and expiration timers, and data storage periods.
  • Provides an overview of DNS configuration parameters for a zone.

Address Records: A and AAAA

  • A record maps a hostname to an IPv4 address; AAAA maps to IPv6.
  • Querying returns the IP tied to the host record for client connections.

Example Details

  • A record example: name www.professormesser.com with IPv4 address 162.59.246.1.164 (as shown).
  • Quad A (AAAA) provides similar mapping for IPv6 using a different record type.

Canonical Name (CNAME) Records

  • Creates aliases pointing to a canonical hostname.
  • Multiple names can reference the same server; client may perform additional lookup to resolve the IP.

CNAME Resolution Flow

  • Query for www.example.com returns alias to mail.example.com.
  • If mail.example.com IP not cached, client performs another lookup for its A/AAAA record.

Mail Exchanger (MX) Records

  • Specifies the mail server for a domain to send/receive email.
  • Requires a corresponding A record to resolve the mail server’s IP before delivery.

Configuration Interface

  • Web-based DNS front ends can edit MX details: target name and TTL (e.g., 15 minutes).

Text (TXT) Records: SPF and DKIM

  • TXT stores human-readable text for various purposes.

SPF (Sender Policy Framework)

  • Declares authorized mail servers allowed to send on behalf of the domain.
  • Receiving servers check SPF TXT to prevent spoofed emails.

DKIM (DomainKeys Identified Mail)

  • Uses digital signatures on emails; receivers verify using the sender’s public key.
  • Public key is stored in a TXT record; keys are long but text-friendly.

Example Details

  • SPF: professormesser.com authorizes mailgun.org server to send mail.
  • DKIM: public key stored in TXT to enable signature verification.

Name Server (NS) Records

  • List authoritative name servers for the domain.
  • Critical for directing queries to the correct DNS servers.

Example Details

  • Domain lists multiple NS entries, such as ns1.example.com and another server.

Pointer (PTR) Records and Reverse DNS

  • Provide reverse lookup: IP address to fully qualified domain name.
  • Stored under reversed IP notation corresponding to subnets.

PTR Resolution Flow

  • PTR entries for joe.example.com, www.example.com, build.example.com with associated reversed IPs.
  • Querying the reverse zone for 192.168.20.10 returns www.example.com as the response.

Key Terms & Definitions

  • Resource Record: A line in DNS containing specific data like IPs or aliases.
  • SOA: Start of Authority; zone parameters and metadata.
  • A Record: IPv4 address mapping for a hostname.
  • AAAA Record: IPv6 address mapping for a hostname.
  • CNAME: Canonical name; alias pointing to another hostname.
  • MX: Mail exchanger; designates mail server for a domain.
  • TXT: Text record; stores SPF, DKIM, and other text data.
  • SPF: Sender Policy Framework; lists authorized outbound mail servers.
  • DKIM: DomainKeys Identified Mail; email signing with public key in DNS.
  • NS: Name server; identifies authoritative DNS servers.
  • PTR: Pointer; reverse DNS mapping from IP to hostname.

Structured Summary

Record TypePurposeExample/Detail
SOAZone metadata and timersSerial, retries, expiration, storage duration
AHostname to IPv4 addresswww.professormesser.com → 162.59.246.1.164
AAAAHostname to IPv6 addressIPv6 mapping using four A’s
CNAMEAlias to canonical namewww.example.com → mail.example.com
MXMail server for domainMail target mail.example.com; TTL 15 minutes
TXT (SPF)Authorized sendersprofessormesser.com authorizes mailgun.org
TXT (DKIM)Stores public key for email signature verificationLong public key in TXT
NSAuthoritative name serversns1.example.com and another NS listed
PTRIP to hostname (reverse DNS)192.168.20.10 → www.example.com

Action Items / Next Steps

  • Ensure MX targets have corresponding A/AAAA records for deliverability.
  • Publish accurate SPF TXT to list all authorized outbound mail servers.
  • Configure DKIM TXT with current public keys for signature verification.
  • Verify NS records list all authoritative servers correctly.
  • Maintain PTR records for key hosts to support reverse lookups.