________________________________
From: Joe Abley <[email protected]>
> I think special in this case means software changes are required in clients
> and servers, e.g. "use this other protocol to resolve names under LOCAL". I
> don't see that for INTERNAL, or CORP, or oweifeowihfoihewfwe, or whatever
> private-use 3166-alpha2 code I mentioned. I don't think INTERNAL is special
> in this way, and I don't understand why people who think INTERNAL is, in
> fact, special don't find CORP and friends special.
RFC 8375 Section 6.3 says
A host that is configured to use a resolver other than one that
has been provided by the local network may be unable to resolve,
or may receive incorrect results for, subdomains of 'home.arpa.'.
In order to avoid this, it is permissible that hosts use the
resolvers that are locally provided for resolving 'home.arpa.',
even when they are configured to use other resolvers.
The IETF has the power to give this same treatment to other names too. Making
a declaration like this for names that might actually be in use would be
foolish, but publishing a statement like this for a name specifically,
permanently reserved by ICANN for this purpose would seem logical. It might
also help to accomplish some of the goals of ".home.arpa", which I suspect has
not gotten as much use as some originally hoped.
--Ben Schwartz
_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]
