RFC 1713: Tools for DNS debugging
In plain English — editorial summary, not part of the RFC
Although widely used (and most of the times unnoticed), DNS (Domain Name System) is too much overlooked, in the sense that people, especially administrators, tend to ignore possible anomalies as long as applications that need name-to-address mapping continue to work. This document presents some tools available for domain administrators to detect and correct those anomalies. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC1713
- Published
- November 1994
- Authors
- A. Romao
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 13
- Also known as
- FYI27
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1712DNS Encoding of Geographical LocationCurrent
November 1994
- RFC 1706DNS NSAP Resource RecordsUpdated
October 1994
- RFC 1637DNS NSAP Resource RecordsObsoleted
June 1994
- RFC 1877PPP Internet Protocol Control Protocol Extensions for Name Server AddressesCurrent
December 1995
- RFC 1538Advanced SNA/IP : A Simple SNA Transport ProtocolCurrent
October 1993
- RFC 1535A Security Problem and Proposed Correction With Widely Deployed DNS SoftwareCurrent
October 1993
- RFC 1912Common DNS Operational and Configuration ErrorsCurrent
February 1996
- RFC 2009GPS-Based Addressing and RoutingCurrent
November 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?