[Ietf-not43] dns mapping

[Eric A. Hall]

on 7/28/2003 10:16 AM Michael.Dillon at radianz.com wrote:

>> For example, the FIRS specification for ASNs currently says that
>> clients must use the LDAP servers associated with the asn.arpa zone
>> by default, while the IPv4 specification says that FIRS clients must
>> use the LDAP servers associated with the in-addr.arpa zone by
>> default, while the IPv6 specification says to use ip6.arpa by
>> default.
> 
> This doesn't make sense. If you are using FIRS to look-up information 
> about the IP address block owner, then the mapping in in-addr.arpa or
> ip6.arpa is useless because it refers to the domain name of the device
> currently USING the address, not the owner of the address block. In a
> block of 256 IPv4 addresses owned by one entity there could be 256
> different user domains.

You misread it. The default mapping is a top-level mapping.

EG, if a user enters *ANY* IPv4 address, the client says "oh this is an
IPv4 address" and issues lookups for _ldap._tcp.in-addr.arpa. The default
is to go ask the LDAP servers associated with the entire IPv4 address
space, not the servers associated with a specific address.

Separately, the model allows a user to override the default behavior and
ask for the servers associated with a particular address, but that's only
provided as a feature, as a way to circumnavigate the delegation servers
in those situations where this would be handy (EG, if there is a ~route
service definition, where user-to-user queries would be useful, and where
the entities are providing the service).

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/