Connected: An Internet Encyclopedia
6.4.2. Inverse query and response example

Up: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1035
Up: 6. NAME SERVER IMPLEMENTATION
Up: 6.4. Inverse queries (Optional)
Prev: 6.4.1. The contents of inverse queries and responses
Next: 6.4.3. Inverse query processing

6.4.2. Inverse query and response example

6.4.2. Inverse query and response example

The overall structure of an inverse query for retrieving the domain name that corresponds to Internet address 10.1.0.52 is shown below:

HeaderOPCODE=IQUERY, ID=997
Question<empty>
Answer<anyname> A IN 10.1.0.52
Authority<empty>
Additional<empty>

This query asks for a question whose answer is the Internet style address 10.1.0.52. Since the owner name is not known, any domain name can be used as a placeholder (and is ignored). A single octet of zero, signifying the root, is usually used because it minimizes the length of the message. The TTL of the RR is not significant. The response to this query might be:

HeaderOPCODE=RESPONSE, ID=997
QuestionQTYPE=A, QCLASS=IN, QNAME=VENERA.ISI.EDU
AnswerVENERA.ISI.EDU A IN 10.1.0.52
Authority<empty>
Additional<empty>

Note that the QTYPE in a response to an inverse query is the same as the TYPE field in the answer section of the inverse query. Responses to inverse queries may contain multiple questions when the inverse is not unique. If the question section in the response is not empty, then the RR in the answer section is modified to correspond to be an exact copy of an RR at the first QNAME.


Next: 6.4.3. Inverse query processing

Connected: An Internet Encyclopedia
6.4.2. Inverse query and response example