Re: Temporary failure in name resolution

From	Curt <curty@free.fr>
Newsgroups	linux.debian.user
Subject	Re: Temporary failure in name resolution
Date	2024-01-12 17:10 +0100
Message-ID	<HVsgy-2C46-5@gated-at.bofh.it> (permalink)
References	(4 earlier) <HUMqZ-2bLR-1@gated-at.bofh.it> <HUNn3-2ckY-11@gated-at.bofh.it> <HUTLP-2gSH-1@gated-at.bofh.it> <HV6g2-2opP-9@gated-at.bofh.it> <HVnTz-2zkC-5@gated-at.bofh.it>
Organization	Unorganized

Show all headers | View raw

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?

>:P
>
>


--

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