Re: Temporary failure in name resolution
On Fri, Jan 12, 2024 at 12:33 PM <debian-user@howorth.org.uk> wrote:
>
> Jeffrey Walton <noloader@gmail.com> wrote:
> > On Fri, Jan 12, 2024 at 11:08 AM Curt <curty@free.fr> wrote:
> > >
> > > On 2024-01-12, debian-user@howorth.org.uk
> > > <debian-user@howorth.org.uk> wrote:
> > > > Curt <curty@free.fr> wrote:
> > > >> On 2024-01-11, Max Nikulin <manikulin@gmail.com> wrote:
> > > >> >
> > > >> > There was a thread that "home" as the top level domain might
> > > >> > not be really safe (somebody might register it). A reserved
> > > >> > domain is "home.arpa" so e.g. to have "thinkpad",
> > > >> > the /etc/hosts entry should be
> > > >> >
> > > >> > 127.0.1.1 thinkpad.home.arpa thinkpad
> > > >> >
> > > >>
> > > >> The .arpa domain is the “Address and Routing Parameter Area”
> > > >> domain and is designated to be used exclusively for
> > > >> Internet-infrastructure purposes.
> > > >>
> > > >> https://www.iana.org/domains/arpa
> > > >
> > > > Indeed, and a little way down that page it says:
> > > >
> > > > home.arpa For non-unique use in residential home networks
> > > > RFC 8375
> > >
> > > I missed that.
> > >
> > > Yet the reserved gTLDs from the 2018 ICANN resolution
> > > are .home, .corp, and .mail. Does home.arpa comply with that
> > > resolution?
> >
> > And to muddy the waters a little more, IANA has some reserved domain
> > names, too:
> > <https://www.iana.org/assignments/special-use-domain-names/special-use-domain-names.xhtml>.
> > Also see <https://www.iana.org/domains/reserved>.
>
> Those references don't seem to muddy the issue. The second refers to
> the first and the first says
>
> home.arpa. [RFC8375]
The fellow asked about .home, .corp, and .mail immediately above.
IANA widens the list to include names like local. and invalid. There
are more names than just the few named in this thread.
Jeff
Reply to: