metasystema.org
CurrentPROPOSED STANDARDIETF stream

RFC 7505: A "Null MX" No Service Resource Record for Domains That Accept No Mail

In plain English — editorial summary, not part of the RFC

Internet mail determines the address of a receiving server through the DNS, first by looking for an MX record and then by looking for an A/AAAA record as a fallback. Unfortunately, this means that the A/AAAA record is taken to be mail server address even when that address does not accept mail. The No Service MX RR, informally called "null MX", formalizes the existing mechanism by which a domain announces that it accepts no mail, without having to provide a mail server; this permits significant operational efficiencies.

Document record

Document ID
RFC7505
Published
June 2015
Authors
J. Levine; M. Delany
Status
PROPOSED STANDARD
Stream
IETF
Area
art
Pages
6
Also known as
—

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/7505-a-null-mx-no-service-resource-record-for-domains-that-accept-no-mail