Re: Proposed resolution: PTR queries for 254.169.in-addr.arpa

Rob Austein <[email protected]> Sun, 24 Apr 2005 14:17:01 -0400
Newsgroups gmane.ietf.zeroconf
Message-ID <[email protected]>
At Fri, 22 Apr 2005 21:14:42 -0700 (PDT), Bernard Aboba wrote:
> 
> Here is a proposed resolution to the Issue:
> 
> "Mapping from IPv4 addresses to host names is conventionally done
> by issuing DNS queries for names of the form,
> "x.x.x.x.in-addr.arpa." When used for link-local addresses, which
> have significance only on the local link, it is inappropriate to
> send such DNS queries beyond the local link.
> DNS clients MUST NOT send unicast DNS queries for any name that
> falls within the "254.169.in-addr.arpa." domain.
> 
> Recursive name servers MUST NOT allow these queries to
> escape the local scope.  Recursive name servers MAY reply
> with RCODE 3, or they MAY silently discard the request.
> 
> By default, recursive name server implementations SHOULD be
> configured to act as if they were authoritative for an
> empty 254.169.in-addr.arpa zone and return RCODE 3 for any
> such query.  Implementations SHOULD allow this default to
> be overridden.

Er, s/SHOULD/MUST/ here.  Hard wiring this into a recursive name
server with no way to override it is probably not wise.

>		  Returning an RCODE 3 is the correct default
> setting because it reduces the query load but also because if
> the site administrator has not set up the reverse tree
> corresponding to IPv4 Link-Local addresses in use,
> returning RCODE 3 is in fact the correct answer."

Other than the above, this seems ok.