All specs
RFC 1034RFCMust KnowBack OfficeProduct1987

Domain Name System — Concepts

Naming & Addressing·RFC Editor
WHY YOU NEED THIS

DNS is the phone book of the internet. Every domain, email MX record, SPF/DKIM TXT record, and service discovery entry depends on it.

What It Defines

Defines the DNS domain namespace, resource records, name servers, resolvers, and the overall architecture for distributed name resolution. This is the conceptual foundation that RFC 1035 implements.

Canonical (Normative)

Convenient (Practical)

Related References

dnsnaminginfrastructure
Standards Body
RFC Editor

The canonical publication point for finalized RFCs. If a protocol is standardized as an RFC, the RFC Editor text is the normative final reference. Published by the IETF, IRTF, IAB, and independent stream.

Visit

Related Specs

RFC 1035RFCMust Know

DNS Implementation

The record types (A, MX, TXT, CNAME) you configure in every DNS panel live in this spec. Know what you're setting.

Back OfficeProductNaming & Addressing
Details
RFC 3986RFCMust Know

URI

Every URL in your app, API, auth redirect, webhook, or deep link is built on this grammar. Essential for routing, redirects, and OAuth callback validation.

Back OfficeProductNaming & Addressing
Details
RFC 7208RFCMust Know

SPF

Without a correct SPF record, your domain's email will fail or be deferred by major receivers (Gmail, Outlook). Set correctly as part of basic email deliverability.

Back OfficeEmail
Details
RFC 6376RFCMust Know

DKIM

DKIM is required to pass DMARC. Without it, your email won't be trusted by major providers. Set up alongside SPF as part of any serious email configuration.

Back OfficeEmail
Details
RFC 7489RFCMust Know

DMARC

DMARC is the final layer of email authentication. Without it, your domain can be spoofed in phishing. Google and Yahoo require DMARC for bulk senders.

Back OfficeEmail
Details