RFC 3258: Distributing Authoritative Name Servers via Shared Unicast Addresses
In plain English — editorial summary, not part of the RFC
This memo describes a set of practices intended to enable an authoritative name server operator to provide access to a single named server in multiple locations. The primary motivation for the development and deployment of these practices is to increase the distribution of Domain Name System (DNS) servers to previously under- served areas of the network topology and to reduce the latency for DNS query responses in those areas. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3258
- Published
- April 2002
- Authors
- T. Hardie
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 11
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3216SMIng ObjectivesCurrent
December 2001
- RFC 3198Terminology for Policy-Based ManagementCurrent
November 2001
- RFC 3169Criteria for Evaluating Network Access Server ProtocolsCurrent
September 2001
- RFC 3127Authentication, Authorization, and Accounting: Protocol EvaluationCurrent
June 2001
- RFC 2889Benchmarking Methodology for LAN Switching DevicesCurrent
August 2000
- RFC 3638Applicability Statement for Reclassification of RFC 1643 to Historic StatusCurrent
October 2003
- RFC 2869RADIUS ExtensionsUpdated
June 2000
- RFC 2868RADIUS Attributes for Tunnel Protocol SupportUpdated
June 2000
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?