RFC 3425:Obsoleting IQUERY
RFC-Ref

RFC - 3425

Obsoleting IQUERY

Original: ftp://ftp.isi.edu/in-notes/rfc3425.txt
Authors: D. Lawrence [Nominum]
Date: November 2002
Category: Proposed Standard



Updates:
RFC-1035std13
[STD 13]
Domain names - implementation and specification (Updated by RFC-1876exp, RFC-1348, RFC-4033prop, RFC-4035prop, RFC-4034prop, RFC-2308prop, RFC-2065, RFC-2845prop, RFC-2181prop, RFC-1995prop, RFC-1996prop, RFC-2535, RFC-4343prop, RFC-3658, RFC-1982prop, RFC-2136prop, RFC-3425prop, RFC-1101, RFC-1183exp, RFC-2137)

Referred by: 3 RFC
Refers to: 3 RFC

Status

This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (2002). All Rights Reserved.

Abstract

The IQUERY method of performing inverse DNS lookups, specified in RFC 1035std13, has not been generally implemented and has usually been operationally disabled where it has been implemented. Both reflect a general view in the community that the concept was unwise and that the widely-used alternate approach of using pointer (PTR) queries and reverse-mapping records is preferable. Consequently, this document deprecates the IQUERY operation, declaring it entirely obsolete. This document updates RFC 1035std13.


About Resource

Google
Web
RFC-Ref