On 1/18/22 1:50 PM, Rich Freeman wrote:
No, I'm talking about the opposite situation. I'm talking about you
have foo.local resolvable via mDNS, but not DNS - then there is a
chance you won't be able to access the host.
It's the same problem just opposite directions.
The solution is to use
>
>-Original Message-
>From: Rich Freeman
>Sent: Tuesday, January 18, 2022 12:50 PM
>To: gentoo-user@lists.gentoo.org
>Subject: Re: [gentoo-user] TLD for home LAN?
>
>On Tue, Jan 18, 2022 at 3:12 PM Laurence Perkins wrote:
>>
>>
>>
>&
On Tue, Jan 18, 2022 at 3:12 PM Laurence Perkins wrote:
>
>
>
> >>-Original Message-
> >>From: Rich Freeman
> >>Sent: Tuesday, January 18, 2022 11:41 AM
> >>To: gentoo-user@lists.gentoo.org
> >>Subject: Re: [gentoo-user] TLD f
>>-Original Message-
>>From: Rich Freeman
>>Sent: Tuesday, January 18, 2022 11:41 AM
>>To: gentoo-user@lists.gentoo.org
>>Subject: Re: [gentoo-user] TLD for home LAN?
>>
>>On Tue, Jan 18, 2022 at 12:28 PM Laurence Perkins
>>wrote:
On Tue, Jan 18, 2022 at 12:28 PM Laurence Perkins wrote:
>
> The standard does not prohibit the names being resolvable via unicast DNS as
> well, though it does recommend that you make sure the two resolution paths
> return consistent results since most systems will take the first response
>
-Original Message-
From: tastytea
Sent: Saturday, January 15, 2022 2:54 AM
>To: gentoo-user@lists.gentoo.org
>Subject: Re: [gentoo-user] TLD for home LAN?
>
>On 2022-01-15 10:33+ Peter Humphrey wrote:
>
>> Hello list,
>>
>> Rich F said recently
On Saturday, 15 January 2022 19:54:13 GMT Grant Taylor wrote:
> On 1/15/22 3:33 AM, Peter Humphrey wrote:
> > Rich F said recently, "I'd avoid using the .local TLD due to RFC 6762."
>
> Ya
--->8
> Ergo, RFC 6762 does not preclude the use of the local top level domain
> in traditional
* tastytea:
> Another solution would be to register an inexpensive domain name and
> use that.
Quite so. For example, Hetzner (no affiliation) charges 3,36 EUR per
year for a .de Domain. An officially registered domain saves a lot of
hassle.
-Ralph
On Sat 15 Jan 2022 11:53:58 GMT, tastytea wrote:
> On 2022-01-15 10:33+ Peter Humphrey wrote:
>
> > Hello list,
> >
> > Rich F said recently, "I'd avoid using the .local TLD due to RFC
> > 6762."
> >
> > That brings me back to a thorny problem: what should I call my local
> > network? It
On Sat, Jan 15, 2022 at 2:54 PM Grant Taylor
wrote:
>
> RFC 6762 does not preclude the use of the local top level domain
> in traditional unicast DNS.
Of course it doesn't. You can also go ahead and use some of Amazon's
AWS IP space to number your home network too if you want. Just don't
be
On Sat, Jan 15, 2022 at 2:35 PM Raphael Mejias Dias wrote:
>>
>> You might want to look into whether it solves your problems
>> out-of-the-box without the need to run internal DNS. The latter still
>> has certain advantages, but mDNS obviously benefits from simplicity.
>>
>>
> This solution,
On 1/15/22 3:33 AM, Peter Humphrey wrote:
Hello list,
Hi.
Rich F said recently, "I'd avoid using the .local TLD due to RFC 6762."
Ya
I've read RFC 6762 in the past and I just skimmed part of it again. I
didn't find anything that prohibited the use of the local top level
domain for
>
> On Sat, Jan 15, 2022 at 5:57 AM William Kenworthy
> wrote:
> >
> > On 15/1/22 18:33, Peter Humphrey wrote:
> > > Hello list,
> > >
> > > Rich F said recently, "I'd avoid using the .local TLD due to RFC 6762."
> > >
> > > That brings me back to a thorny problem: what should I call my local
>
On Sat, Jan 15, 2022 at 5:57 AM William Kenworthy wrote:
>
> On 15/1/22 18:33, Peter Humphrey wrote:
> > Hello list,
> >
> > Rich F said recently, "I'd avoid using the .local TLD due to RFC 6762."
> >
> > That brings me back to a thorny problem: what should I call my local
> > network?
> > It
tastytea wrote:
>
> Another solution would be to register an inexpensive domain name and use
> that.
That's generally a good idea. After using .local for many years,
too, I have switched to my "official" domain and added "local"
for the internal IP addresses.
So my server down in the basement
On 15/1/22 18:33, Peter Humphrey wrote:
Hello list,
Rich F said recently, "I'd avoid using the .local TLD due to RFC 6762."
That brings me back to a thorny problem: what should I call my local network?
It used to be .prhnet, but then a program I tried a few years ago insisted on
a
On 2022-01-15 10:33+ Peter Humphrey wrote:
> Hello list,
>
> Rich F said recently, "I'd avoid using the .local TLD due to RFC
> 6762."
>
> That brings me back to a thorny problem: what should I call my local
> network? It used to be .prhnet, but then a program I tried a few
> years ago
17 matches
Mail list logo
