Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #265837

Re: Temporary failure in name resolution

Show all headers | View raw

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>.

Jeff

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Temporary failure in name resolution Rodolfo Medina <rodolfo.medina@gmail.com> - 2024-01-10 19:20 +0100
  Re: Temporary failure in name resolution <tomas@tuxteam.de> - 2024-01-10 19:30 +0100
    Re: Temporary failure in name resolution Rodolfo Medina <rodolfo.medina@gmail.com> - 2024-01-10 19:40 +0100
      Re: Temporary failure in name resolution Greg Wooledge <greg@wooledge.org> - 2024-01-10 19:50 +0100
        Re: Temporary failure in name resolution Rodolfo Medina <rodolfo.medina@gmail.com> - 2024-01-10 20:30 +0100
          Re: Temporary failure in name resolution Marco Moock <mm@dorfdsl.de> - 2024-01-10 20:30 +0100
          Re: Temporary failure in name resolution Greg Wooledge <greg@wooledge.org> - 2024-01-10 21:30 +0100
            Re: Temporary failure in name resolution Max Nikulin <manikulin@gmail.com> - 2024-01-11 04:20 +0100
              Re: Temporary failure in name resolution Greg Wooledge <greg@wooledge.org> - 2024-01-11 04:30 +0100
                Re: Temporary failure in name resolution Max Nikulin <manikulin@gmail.com> - 2024-01-12 04:10 +0100
              Re: Temporary failure in name resolution David Wright <deblis@lionunicorn.co.uk> - 2024-01-11 06:00 +0100
              Re: Temporary failure in name resolution Curt <curty@free.fr> - 2024-01-11 17:40 +0100
                Re: Temporary failure in name resolution Marco Moock <mm@dorfdsl.de> - 2024-01-11 18:10 +0100
                Re: Temporary failure in name resolution debian-user@howorth.org.uk - 2024-01-12 12:30 +0100
                Re: Temporary failure in name resolution Byung-Hee HWANG <soyeomul@doraji.xyz> - 2024-01-12 14:10 +0100
                Re: Temporary failure in name resolution Curt <curty@free.fr> - 2024-01-12 17:10 +0100
                Re: Temporary failure in name resolution Jeffrey Walton <noloader@gmail.com> - 2024-01-12 17:30 +0100
                Re: Temporary failure in name resolution Jeffrey Walton <noloader@gmail.com> - 2024-01-12 18:40 +0100
                Re: Temporary failure in name resolution debian-user@howorth.org.uk - 2024-01-12 18:40 +0100
                Re: Temporary failure in name resolution John Hasler <john@sugarbit.com> - 2024-01-12 20:50 +0100
                Re: Temporary failure in name resolution debian-user@howorth.org.uk - 2024-01-12 19:20 +0100
          Re: Temporary failure in name resolution <tomas@tuxteam.de> - 2024-01-11 06:30 +0100

csiph-web