RFC 5625: DNS Proxy Implementation Guidelines
In plain English — editorial summary, not part of the RFC
This document provides guidelines for the implementation of DNS proxies, as found in broadband gateways and other similar network devices. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC5625
- Published
- August 2009
- Authors
- R. Bellis
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- int
- Pages
- 12
- Also known as
- BCP152
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5966DNS Transport over TCP - Implementation RequirementsObsoleted
August 2010
- RFC 5205Host Identity Protocol (HIP) Domain Name System (DNS) ExtensionsObsoleted
April 2008
- RFC 6097Local Mobility Anchor (LMA) Discovery for Proxy Mobile IPv6Current
February 2011
- RFC 6418Multiple Interfaces and Provisioning Domains Problem StatementCurrent
November 2011
- RFC 4703Resolution of Fully Qualified Domain Name (FQDN) Conflicts among Dynamic Host Configuration Protocol (DHCP) ClientsCurrent
October 2006
- RFC 6604xNAME RCODE and Status Bits ClarificationCurrent
April 2012
- RFC 4635HMAC SHA (Hashed Message Authentication Code, Secure Hash Algorithm) TSIG Algorithm IdentifiersObsoleted
August 2006
- RFC 6731Improved Recursive DNS Server Selection for Multi-Interfaced NodesCurrent
December 2012
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?