| 1 |
On Saturday, 15 January 2022 19:54:13 GMT Grant Taylor wrote: |
| 2 |
> On 1/15/22 3:33 AM, Peter Humphrey wrote: |
| 3 |
|
| 4 |
> > Rich F said recently, "I'd avoid using the .local TLD due to RFC 6762." |
| 5 |
> |
| 6 |
> Ya.... |
| 7 |
|
| 8 |
--->8 |
| 9 |
|
| 10 |
> Ergo, RFC 6762 does not preclude the use of the local top level domain |
| 11 |
> in traditional unicast DNS. |
| 12 |
|
| 13 |
OK. |
| 14 |
|
| 15 |
> > That brings me back to a thorny problem: what should I call my local |
| 16 |
> > network? |
| 17 |
> |
| 18 |
> Maybe it's just me, I'm weird like that, but I vehemently believe that |
| 19 |
> *I* am the authority for the names of *MY* network(s). As such, |
| 20 |
> whatever name /I/ choose is the name that /my/ network(s) will use. |
| 21 |
|
| 22 |
And as the addresses are all unroutable outside the LAN, that could be |
| 23 |
anything. |
| 24 |
|
| 25 |
--->8 |
| 26 |
|
| 27 |
> > It used to be .prhnet, but then a program I tried a few years ago |
| 28 |
> > insisted on a two-component name, so I changed it to .prhnet.local. |
| 29 |
> |
| 30 |
> There are /some/ complications that may have some influence on what |
| 31 |
> names are chosen. |
| 32 |
> |
| 33 |
> But I point out that your network quite likely did exactly what you |
| 34 |
> wanted to do up until that point. |
| 35 |
|
| 36 |
It did, yes. |
| 37 |
|
| 38 |
> Q: Did you continue to use the software that you tried? Or did you end |
| 39 |
> up renaming your network for something that you are no longer using? }:-) |
| 40 |
|
| 41 |
No and yes, in that order. Guilty as charged. :) |
| 42 |
|
| 43 |
--->8 |
| 44 |
|
| 45 |
> I really feel like RFC 6762 is a "you might want to consider not using |
| 46 |
> the .local top level domain on the off hand chance that you ever have |
| 47 |
> something that can't / won't work with it." |
| 48 |
> |
| 49 |
> > I suppose it's possible that someone may want to connect an Apple |
| 50 |
> > device to my network, so perhaps I should clear the way for that |
| 51 |
> > eventuality. |
| 52 |
> |
| 53 |
> Is that possibility significant enough to influence how /you/ run /your/ |
| 54 |
> network? |
| 55 |
|
| 56 |
Could be. I occasionally take my machine to my daughter's house, and she's an |
| 57 |
Apple person. This is one reason for my current musing. |
| 58 |
|
| 59 |
Thanks Grant. I think I've been worrying needlessly. The network will revert |
| 60 |
to its original name. |
| 61 |
|
| 62 |
-- |
| 63 |
Regards, |
| 64 |
Peter. |
Archives