On Jan 30, 2017, at 1:26 PM, Ralph Droms <[email protected]> wrote:
> Name resolution APIs and libraries MUST NOT recognize names that end in
> '.homenet.' as special and MUST NOT treat them differently. Name resolution
> APIs will only resolve such a name correctly if the query is sent to a
> recursive DNS server configured to be authoritative for the .homenet zone
> appropriate to the home network. This RDNSS or list of RDNSSes will usually
> be supplied to the client through a local configuration mechanism like HNCP
> or DHCP. If a host is configured to use a resolver other than one that is
> authoritative for the appropriate .homenet zone, the client may be unable to
> resolve or receive incorrect results for names in sub domains of ".homenet".
How about this:
> Name resolution APIs and libraries MUST NOT recognize names that end in
> '.homenet.' as special and MUST NOT treat them differently. Name resolution
> APIs MUST send queries for such names to a recursive DNS server that is
> configured to be authoritative for the .homenet zone appropriate to the home
> network. One or more IP addresses for recursive DNS servers will usually be
> supplied to the client through router advertisements or DHCP. If a host is
> configured to use a resolver other than one that is authoritative for the
> appropriate .homenet zone, the client may be unable to resolve, or may
> receive incorrect results for, names in sub domains of ".homenet".
I don't like RDNSS, so I expanded the acronym; I don't think that we should
mention HNCP here as a host configuration protocol. I also cleaned up the
last sentence a bit.
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
