RFC 1536: Common DNS Implementation Errors and Suggested Fixes
In plain English — editorial summary, not part of the RFC
This memo describes common errors seen in DNS implementations and suggests some fixes. This memo provides information for the Internet community. It does not specify an Internet standard.
Document record
- Document ID
- RFC1536
- Published
- October 1993
- Authors
- A. Kumar; J. Postel; C. Neuman; P. Danzig; S. Miller
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- app
- Pages
- 12
- Also known as
- —
- Updated by:
- RFC 9210
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1537Common DNS Data File Configuration ErrorsObsoleted
October 1993
- RFC 1611DNS Server MIB ExtensionsCurrent
May 1994
- RFC 1612DNS Resolver MIB ExtensionsCurrent
May 1994
- RFC 1664Using the Internet DNS to Distribute RFC1327 Mail Address Mapping TablesObsoleted
August 1994
- RFC 1794DNS Support for Load BalancingCurrent
April 1995
- RFC 2219Use of DNS Aliases for Network ServicesCurrent
October 1997
- RFC 1886DNS Extensions to support IP version 6Obsoleted
December 1995
- RFC 1982Serial Number ArithmeticCurrent
August 1996
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?