Re: Domain name to use on home networks

On 10/30/23 21:32, Charles Curley wrote: On Mon, 30 Oct 2023 14:43:43 -0400 Greg Wooledge wrote: …but for Gene's systems I would recommend traditional Debian ifupdown (/etc/network/interfaces). It's by far the simplest, and the most widely supported among the community, in case he has

Re: Domain name to use on home networks

On 31/10/2023 01:43, Greg Wooledge wrote: for Gene's systems I would recommend traditional Debian ifupdown (/etc/network/interfaces). It's by far the simplest, and the most widely supported among the community, in case he has questions. Notice that in the default configuration NetworkManager

Re: Domain name to use on home networks

On 30/10/2023 23:09, gene heskett wrote: Making resolv.conf immutable seems to be the way to permanently insulate me from NM's broken idea of whats right. Gene, from what you have written in this thread I see nothing wrong in behavior of NetworkManager. Certainly it is easier to continue

Re: Domain name to use on home networks

On Mon, 30 Oct 2023 14:43:43 -0400 Greg Wooledge wrote: > …but for Gene's systems I would recommend > traditional Debian ifupdown (/etc/network/interfaces). It's by far > the simplest, and the most widely supported among the community, in > case he has questions. It has the further advantage

Re: Domain name to use on home networks

On 10/30/23 14:44, Greg Wooledge wrote: On Mon, Oct 30, 2023 at 06:37:48PM +, Andrew M.A. Cater wrote: On Mon, Oct 30, 2023 at 02:29:37PM -0400, gene heskett wrote: On 10/30/23 13:40, John Hasler wrote: I wrote: Why do you have NetworkManager installed at all? Gene writes: Std image

Re: Domain name to use on home networks

On 10/30/23 14:43, Greg Wooledge wrote: On Mon, Oct 30, 2023 at 06:37:48PM +, Andrew M.A. Cater wrote: On Mon, Oct 30, 2023 at 02:29:37PM -0400, gene heskett wrote: On 10/30/23 13:40, John Hasler wrote: I wrote: Why do you have NetworkManager installed at all? Gene writes: Std image

Re: Domain name to use on home networks

On 10/30/23 14:30, gene heskett wrote: On 10/30/23 13:40, John Hasler wrote: I wrote: Why do you have NetworkManager installed at all? Gene writes: Std image dd'd to u-sd card install on the arm64 stuff, can't get away from it. Why won't "sudo apt remove --purge network-manager" work for

Re: Domain name to use on home networks

On Mon, Oct 30, 2023 at 06:37:48PM +, Andrew M.A. Cater wrote: > On Mon, Oct 30, 2023 at 02:29:37PM -0400, gene heskett wrote: > > On 10/30/23 13:40, John Hasler wrote: > > > I wrote: > > > > Why do you have NetworkManager installed at all? > > > > > > Gene writes: > > > > Std image dd'd to

Re: Domain name to use on home networks

On Mon, Oct 30, 2023 at 02:29:37PM -0400, gene heskett wrote: > On 10/30/23 13:40, John Hasler wrote: > > I wrote: > > > Why do you have NetworkManager installed at all? > > > > Gene writes: > > > Std image dd'd to u-sd card install on the arm64 stuff, can't get away > > > from it. > > > > Why

Re: Domain name to use on home networks

On 10/30/23 13:40, John Hasler wrote: I wrote: Why do you have NetworkManager installed at all? Gene writes: Std image dd'd to u-sd card install on the arm64 stuff, can't get away from it. Why won't "sudo apt remove --purge network-manager" work for you? It did, but took the network down

Re: Domain name to use on home networks

I wrote: > Why do you have NetworkManager installed at all? Gene writes: > Std image dd'd to u-sd card install on the arm64 stuff, can't get away > from it. Why won't "sudo apt remove --purge network-manager" work for you? -- John Hasler j...@sugarbit.com Elmwood, WI USA

Re: Domain name to use on home networks

On 10/30/23 13:29, gene heskett wrote: On 10/30/23 12:48, Pocket wrote: On 10/30/23 12:43, gene heskett wrote: On 10/30/23 12:16, John Hasler wrote: Why do you have NetworkManager installed at all? Std image dd'd to u-sd card install on the arm64 stuff, can't get away from it. You can

Re: Domain name to use on home networks

On 10/30/23 13:29, Pocket wrote: On 10/30/23 13:21, Pocket wrote: apt purge network-manager This is what I get running the above sudo apt purge network-manager Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were

Re: Domain name to use on home networks

On 10/30/23 13:21, Pocket wrote: On 10/30/23 13:09, gene heskett wrote: On 10/30/23 12:40, Pocket wrote: On 10/30/23 12:15, John Hasler wrote: Why do you have NetworkManager installed at all? That is an interesting question for Gene. apt purge --autoremove network-manager will fix that.

Re: Domain name to use on home networks

On 10/30/23 12:48, Pocket wrote: On 10/30/23 12:43, gene heskett wrote: On 10/30/23 12:16, John Hasler wrote: Why do you have NetworkManager installed at all? Std image dd'd to u-sd card install on the arm64 stuff, can't get away from it. You can only make it somewhere near right and sudo

Re: Domain name to use on home networks

On 10/30/23 13:21, Pocket wrote: apt purge network-manager This is what I get running the above sudo apt purge network-manager Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no

Re: Domain name to use on home networks

On 10/30/23 13:09, gene heskett wrote: On 10/30/23 12:40, Pocket wrote: On 10/30/23 12:15, John Hasler wrote: Why do you have NetworkManager installed at all? That is an interesting question for Gene. apt purge --autoremove network-manager will fix that. I can do that?  The last 3 or 4

Re: Domain name to use on home networks

On 10/30/23 12:40, Pocket wrote: On 10/30/23 12:15, John Hasler wrote: Why do you have NetworkManager installed at all? That is an interesting question for Gene. apt purge --autoremove network-manager will fix that. I can do that? The last 3 or 4 times I tried that, dependencies took the

Re: Domain name to use on home networks

On 10/30/23 12:43, gene heskett wrote: On 10/30/23 12:16, John Hasler wrote: Why do you have NetworkManager installed at all? Std image dd'd to u-sd card install on the arm64 stuff, can't get away from it. You can only make it somewhere near right and sudo chattr +i the files before

Re: Domain name to use on home networks

On 10/30/23 12:16, John Hasler wrote: Why do you have NetworkManager installed at all? Std image dd'd to u-sd card install on the arm64 stuff, can't get away from it. You can only make it somewhere near right and sudo chattr +i the files before networkmangler discovers you've fixed it.

Re: Domain name to use on home networks

On 10/30/23 12:15, John Hasler wrote: Why do you have NetworkManager installed at all? That is an interesting question for Gene. apt purge --autoremove network-manager will fix that. I take a bit different opinion from Gene, instead of chattr +i /etc/resolv.conf I work to figure out how

Re: Domain name to use on home networks

On 10/30/23 10:57, Max Nikulin wrote: On 29/10/2023 23:24, gene heskett wrote: finally solved by editing resolv.conf to put the nameserver address into it, followed by a chattr +i resolv.conf. I have no d clue where mangler I have realized that it is a nice stance taking into account that

Re: Domain name to use on home networks

On 10/30/23 08:25, Greg Wooledge wrote: On Mon, Oct 30, 2023 at 08:19:24AM -0400, Pocket wrote: On 10/30/23 03:54, gene heskett wrote: [ipv4] address1=192.168.71.55/24,192.168.71.1 dns=192.168.71.1; dns-search=hosts;nameserver; ^ this is incorrect nmcli connection

Re: Domain name to use on home networks

Why do you have NetworkManager installed at all? -- John Hasler j...@sugarbit.com Elmwood, WI USA

Re: Domain name to use on home networks

On 10/30/23 08:20, Pocket wrote: On 10/30/23 03:54, gene heskett wrote: On 10/29/23 22:17, Max Nikulin wrote: On 30/10/2023 00:08, Pocket wrote: On 10/29/23 12:24, gene heskett wrote: I have also made a very painfull attempt to change my domainname from coyote.den to home.arpa, and finally

Re: Domain name to use on home networks

On 10/30/23 05:15, Timothy M Butterworth wrote: On Mon, Oct 30, 2023 at 3:55 AM gene heskett > wrote: On 10/29/23 22:17, Max Nikulin wrote: > On 30/10/2023 00:08, Pocket wrote: >> On 10/29/23 12:24, gene heskett wrote: >>> I have also made a

Re: Domain name to use on home networks

On 29/10/2023 23:24, gene heskett wrote: finally solved by editing resolv.conf to put the nameserver address into it, followed by a chattr +i resolv.conf. I have no d clue where mangler I have realized that it is a nice stance taking into account that the topic of the original thread was

Re: Domain name to use on home networks

On 10/30/23 08:24, Greg Wooledge wrote: On Mon, Oct 30, 2023 at 08:19:24AM -0400, Pocket wrote: On 10/30/23 03:54, gene heskett wrote: [ipv4] address1=192.168.71.55/24,192.168.71.1 dns=192.168.71.1; dns-search=hosts;nameserver; ^ this is incorrect nmcli connection

Re: Domain name to use on home networks

On Mon, Oct 30, 2023 at 08:19:24AM -0400, Pocket wrote: > On 10/30/23 03:54, gene heskett wrote: > > [ipv4] > > address1=192.168.71.55/24,192.168.71.1 > > dns=192.168.71.1; > > dns-search=hosts;nameserver; > > > ^ > > this is incorrect > > nmcli connection modify

Re: Domain name to use on home networks

On 10/30/23 08:19, Pocket wrote: On 10/30/23 03:54, gene heskett wrote: On 10/29/23 22:17, Max Nikulin wrote: On 30/10/2023 00:08, Pocket wrote: On 10/29/23 12:24, gene heskett wrote: I have also made a very painfull attempt to change my domainname from coyote.den to home.arpa, and finally

Re: Domain name to use on home networks

On 10/30/23 03:54, gene heskett wrote: On 10/29/23 22:17, Max Nikulin wrote: On 30/10/2023 00:08, Pocket wrote: On 10/29/23 12:24, gene heskett wrote: I have also made a very painfull attempt to change my domainname from coyote.den to home.arpa, and finally reverted that, Gene, have you

Re: Domain name to use on home networks

On Mon, Oct 30, 2023 at 3:55 AM gene heskett wrote: > On 10/29/23 22:17, Max Nikulin wrote: > > On 30/10/2023 00:08, Pocket wrote: > >> On 10/29/23 12:24, gene heskett wrote: > >>> I have also made a very painfull attempt to change my domainname from > >>> coyote.den to home.arpa, and finally

Re: Domain name to use on home networks

On 10/29/23 22:17, Max Nikulin wrote: On 30/10/2023 00:08, Pocket wrote: On 10/29/23 12:24, gene heskett wrote: I have also made a very painfull attempt to change my domainname from coyote.den to home.arpa, and finally reverted that, Gene, have you posted what exactly you did to switch from

Re: Domain name to use on home networks

On 30/10/2023 01:21, Jeffrey Walton wrote: Also see , where the systemd folks said to modify the hostname by hand because hostnamectl butchered the fully qualified hostname. Debian

Re: Domain name to use on home networks

On 30/10/2023 00:08, Pocket wrote: On 10/29/23 12:24, gene heskett wrote: I have also made a very painfull attempt to change my domainname from coyote.den to home.arpa, and finally reverted that, Gene, have you posted what exactly you did to switch from coyote.den to home.arpa? You have

Re: Domain name to use on home networks

Gene writes: > possibly, its a Buffalo Netfinity with a now elderly dd-wrt reflash, > and whose pw I've long since forgot, and its 30 chars of random > gibberish IIRC. Write the password on the router. Write all your passwords down. -- John Hasler j...@sugarbit.com Elmwood, WI USA

Re: Domain name to use on home networks

On Fri, Oct 27, 2023 at 3:14 PM Andrew M.A. Cater wrote: > > On Fri, Oct 27, 2023 at 09:30:09AM -0400, Pocket wrote: > > > > > On Oct 27, 2023, at 9:05 AM, Greg Wooledge wrote: > > > > > > On Fri, Oct 27, 2023 at 07:59:00AM -0400, Pocket wrote: > > >>> On 10/27/23 07:50, Greg Wooledge wrote: >

Re: Domain name to use on home networks

On 10/29/23 13:09, Pocket wrote: On 10/29/23 12:24, gene heskett wrote: On 10/29/23 10:23, David Wright wrote: On Fri 27 Oct 2023 at 11:13:59 (-0400), gene heskett wrote: You saw my hosts entry in the last post, but again 192.168.71.3    coyote.home.arpa    coyote but after a reboot,

Re: Domain name to use on home networks

On 10/29/23 12:24, gene heskett wrote: On 10/29/23 10:23, David Wright wrote: On Fri 27 Oct 2023 at 11:13:59 (-0400), gene heskett wrote: You saw my hosts entry in the last post, but again 192.168.71.3    coyote.home.arpa    coyote but after a reboot, domainname returns none, and the

Re: Domain name to use on home networks

On 10/29/23 10:23, David Wright wrote: On Fri 27 Oct 2023 at 11:13:59 (-0400), gene heskett wrote: You saw my hosts entry in the last post, but again 192.168.71.3coyote.home.arpacoyote but after a reboot, domainname returns none, and the /etc/domainname file has been deleted. As in

Re: Domain name to use on home networks

On 27/10/2023 21:19, Greg Wooledge wrote: More importantly, why on earth would this be recommended over editing the /etc/hostname file, which is *much* simpler, and which appears to be independent of the init system that's in use? hostnamectl tries to prevent split brain /etc/hostname vs.

Re: Domain name to use on home networks

David Wright writes: > I'm just wondering where this file /etc/domainname came from in the > first place. I can't find it with apt-file (killing two birds): Gene created it, having been confused by the hostname man page. -- John Hasler j...@sugarbit.com Elmwood, WI USA

Re: Domain name to use on home networks

On Sun, Oct 29, 2023 at 09:22:38AM -0500, David Wright wrote: > I'm just wondering where this file /etc/domainname came from in the > first place. I can't find it with apt-file (killing two birds): > > $ apt-file find etc/domain > $ I'm assuming either Gene created it himself, because he

Re: Domain name to use on home networks

On Fri 27 Oct 2023 at 11:13:59 (-0400), gene heskett wrote: > You saw my hosts entry in the last post, but again > 192.168.71.3coyote.home.arpacoyote > but after a reboot, domainname returns none, and the /etc/domainname > file has been deleted. As in not visible to an ls of /etc.

Re: Domain name to use on home networks

On 28/10/2023 05:48, Jeffrey Walton wrote: Yeah, just file a bug and let whomever else deal with it. Whatever text is proposed, it will be rejected in favor of what the person with check-in privileges wants. Or worse, the person with check-in privileges will torture the submitter with an

Re: Domain name to use on home networks

On Fri, Oct 27, 2023 at 2:04 PM Greg Wooledge wrote: > > On Fri, Oct 27, 2023 at 12:53:40PM -0500, John Hasler wrote: > > The NIS stuff should be evicted from the hostname man page. > > Well... maybe? While the use of NIS hostname resolution is strongly > discouraged, it's not *forbidden*. A

Re: Domain name to use on home networks

Am 27.10.2023 um 12:09:23 Uhr schrieb gene heskett: > On 10/27/23 10:40, Marco M. wrote: > > Am 27.10.2023 um 10:37:12 Uhr schrieb gene heskett: > > > >> Its in there, for this machine, but on a reboot, the domainname > >> reverts to "none" Apparently I didn't use the approved systemd way > >>

Re: Domain name to use on home networks

On 2023-10-27 at 14:57, John Hasler wrote: > I wrote: > Greg writes: >> My Debian 12 system does not have an /etc/init.d/hostname.sh file, >> or anything else that's close to it. > > My desktop, which has been upgraded many times, does have > /etc/init.d/hostname.sh. However, a recently

Re: Domain name to use on home networks

I wrote: > The NIS stuff should be evicted from the hostname man page. Greg writes: > Well... maybe? While the use of NIS hostname resolution is strongly > discouraged, it's not *forbidden*. A system admin might, in theory, > be using NIS to serve up hostname/IP mappings, in which case the NIS

Re: Domain name to use on home networks

On Fri, Oct 27, 2023 at 12:53:40PM -0500, John Hasler wrote: > The NIS stuff should be evicted from the hostname man page. Well... maybe? While the use of NIS hostname resolution is strongly discouraged, it's not *forbidden*. A system admin might, in theory, be using NIS to serve up hostname/IP

Re: Domain name to use on home networks

The NIS stuff should be evicted from the hostname man page. -- John Hasler j...@sugarbit.com Elmwood, WI USA

Re: Domain name to use on home networks

On Fri, Oct 27, 2023 at 12:46:16PM -0400, gene heskett wrote: > So this is what I get now: > gene@coyote:/etc$ dnsdomainname > home.arpa > gene@coyote:/etc$ hostname > coyote.home.arpa > gene@coyote:/etc$ cat hostname > coyote > Is that correct and will it withstand a reboot? Your hostname will

Re: Domain name to use on home networks

On Fri, Oct 27, 2023 at 11:23:19AM -0500, John Hasler wrote: > Gene writes: > > Define NIS please. > > Network Information Service. You've never heard of it because it's > obsolete. You should ignore it. > > Originally known as

Re: Domain name to use on home networks

On 27 Oct 2023 17:02 +, from 2695bd53d...@ewoof.net (Michael Kjörling): >> HOSTNAME(1) Linux Programmer's Manual HOSTNAME(1) >> >> NAME >>hostname - show or set the system's host name >>domainname - show or set the system's NIS/YP domain name >>

Re: Domain name to use on home networks

On 27 Oct 2023 11:45 -0500, from j...@sugarbit.com (John Hasler): >> Here are the first lines of 'man domainname" : > > That doesn't help very much with no hint as to what NIS is and that it > isn't relevant to DNS. The part of the beginning of that man page which Erwan didn't quote does seem a

Re: Domain name to use on home networks

Le 27/10/2023 à 18:45, John Hasler a écrit : Erwan writes: Here are the first lines of 'man domainname" : That doesn't help very much with no hint as to what NIS is and that it isn't relevant to DNS. it is said later in the man Don't use the command domainname to get the DNS domain name

Re: Domain name to use on home networks

On 10/27/23 12:26, gene heskett wrote: On 10/27/23 11:43, Greg Wooledge wrote: On Fri, Oct 27, 2023 at 11:13:59AM -0400, gene heskett wrote: You saw my hosts entry in the last post, but again 192.168.71.3    coyote.home.arpa    coyote That looks fine to me. but after a reboot,

Re: Domain name to use on home networks

Erwan writes: > Here are the first lines of 'man domainname" : That doesn't help very much with no hint as to what NIS is and that it isn't relevant to DNS. -- John Hasler j...@sugarbit.com Elmwood, WI USA

Re: Domain name to use on home networks

Le 27/10/2023 à 18:30, gene heskett a écrit : On 10/27/23 11:45, Greg Wooledge wrote: On Fri, Oct 27, 2023 at 11:25:00AM -0400, gene heskett wrote: Not a systemd luver nor expert. Someone suggested that if I was using dotted names, then I should edit (as sudo) /etc/hostname which I have now

Re: Domain name to use on home networks

On 10/27/23 11:45, Greg Wooledge wrote: On Fri, Oct 27, 2023 at 11:25:00AM -0400, gene heskett wrote: Not a systemd luver nor expert. Someone suggested that if I was using dotted names, then I should edit (as sudo) /etc/hostname which I have now done t add the FQDN name of coyote.home.arpa.

Re: Domain name to use on home networks

On 10/27/23 11:43, Greg Wooledge wrote: On Fri, Oct 27, 2023 at 11:13:59AM -0400, gene heskett wrote: You saw my hosts entry in the last post, but again 192.168.71.3coyote.home.arpacoyote That looks fine to me. but after a reboot, domainname returns none, and the /etc/domainname

Re: Domain name to use on home networks

Gene writes: > Define NIS please. Network Information Service. You've never heard of it because it's obsolete. You should ignore it. -- John Hasler j...@sugarbit.com Elmwood, WI USA

Re: Domain name to use on home networks

On 10/27/23 10:49, Greg Wooledge wrote: On Fri, Oct 27, 2023 at 10:37:12AM -0400, gene heskett wrote: Its in there, for this machine, but on a reboot, the domainname reverts to "none" Apparently I didn't use the approved systemd way to change it. from a cat of /etc/hosts: 192.168.71.3

Re: Domain name to use on home networks

On 10/27/23 10:40, Marco M. wrote: Am 27.10.2023 um 10:37:12 Uhr schrieb gene heskett: Its in there, for this machine, but on a reboot, the domainname reverts to "none" Apparently I didn't use the approved systemd way to change it. from a cat of /etc/hosts: 192.168.71.3coyote.home.arpa

Re: Domain name to use on home networks

On 10/27/23 10:22, Greg Wooledge wrote: On Fri, Oct 27, 2023 at 02:00:21PM +, Andrew M.A. Cater wrote: On Oct 27, 2023, at 9:05 AM, Greg Wooledge wrote: If you're using short-form hostnames like this: unicorn:~$ hostname unicorn then yeah, [/etc/hosts is] all you need. If you're using

Re: Domain name to use on home networks

On 10/27/23 10:11, Pocket wrote: Sent from my iPad On Oct 27, 2023, at 10:00 AM, Andrew M.A. Cater wrote: On Fri, Oct 27, 2023 at 09:30:09AM -0400, Pocket wrote: Sent from my iPad On Oct 27, 2023, at 9:05 AM, Greg Wooledge wrote: On Fri, Oct 27, 2023 at 07:59:00AM -0400, Pocket

Re: Domain name to use on home networks

On Fri, Oct 27, 2023 at 11:25:00AM -0400, gene heskett wrote: > Not a systemd luver nor expert. Someone suggested that if I was using dotted > names, then I should edit (as sudo) /etc/hostname which I have now done t > add the FQDN name of coyote.home.arpa. You should undo that. There's no

Re: Domain name to use on home networks

On Fri, Oct 27, 2023 at 11:13:59AM -0400, gene heskett wrote: > You saw my hosts entry in the last post, but again > 192.168.71.3coyote.home.arpacoyote That looks fine to me. > but after a reboot, domainname returns none, and the /etc/domainname file ! > So I just sudo edited

Re: Domain name to use on home networks

On 10/27/23 07:59, Pocket wrote: On 10/27/23 07:50, Greg Wooledge wrote: On Fri, Oct 27, 2023 at 07:29:20AM -0400, Pocket wrote: On 10/27/23 07:12, gene heskett wrote: I tried to change just this machine to see how its done, and managed to get all the right answers, which did not affect my

Re: Domain name to use on home networks

On 10/27/23 07:50, Greg Wooledge wrote: On Fri, Oct 27, 2023 at 07:29:20AM -0400, Pocket wrote: On 10/27/23 07:12, gene heskett wrote: I tried to change just this machine to see how its done, and managed to get all the right answers, which did not affect my local network since I generally use

Re: Domain name to use on home networks

On 2023-10-26 09:16, Michael Kjörling wrote: On 25 Oct 2023 21:23 -0400, from monn...@iro.umontreal.ca (Stefan Monnier): If you go with the domain name home.arpa and an IPv4 subnet sliced out of one of 192.168.0.0/16, 172.12.0.0/12 or 10.0.0.0/8, you can be _almost certain_ that nothing will

Re: Domain name to use on home networks

On Fri, Oct 27, 2023 at 10:37:12AM -0400, gene heskett wrote: > Its in there, for this machine, but on a reboot, the domainname reverts to > "none" Apparently I didn't use the approved systemd way to change it. > from a cat of /etc/hosts: > 192.168.71.3coyote.home.arpacoyote What

Re: Domain name to use on home networks

Am 27.10.2023 um 10:37:12 Uhr schrieb gene heskett: > Its in there, for this machine, but on a reboot, the domainname > reverts to "none" Apparently I didn't use the approved systemd way to > change it. from a cat of /etc/hosts: > 192.168.71.3coyote.home.arpacoyote That is only

Re: Domain name to use on home networks

On 10/27/23 07:29, Pocket wrote: On 10/27/23 07:12, gene heskett wrote: On 10/27/23 00:47, Stefan Monnier wrote: I would have thought that techies understand its origins, and non-techies are fairly unlikely ever to encounter it. That's the thing: if you use `home.arpa` for your home

Re: Domain name to use on home networks

On Fri 27 Oct 2023 at 07:12:48 (-0400), gene heskett wrote: > On 10/27/23 00:47, Stefan Monnier wrote: > > > I would have thought that techies understand its origins, and > > > non-techies are fairly unlikely ever to encounter it. > > > > That's the thing: if you use `home.arpa` for your home

Re: Domain name to use on home networks

On Fri, Oct 27, 2023 at 02:00:21PM +, Andrew M.A. Cater wrote: > > > On Oct 27, 2023, at 9:05 AM, Greg Wooledge wrote: > > >>> If you're using short-form hostnames like this: > > >>> > > >>> unicorn:~$ hostname > > >>> unicorn > > >>> > > >>> then yeah, [/etc/hosts is] all you need. If

Re: Changing host name and domain name on Debian; was: Domain name to use on home networks

On 27 Oct 2023 09:30 -0400, from poc...@columbus.rr.com (Pocket): >> If you're a long form hostname person, then your hostname should be set >> to the FQDN of the system. > > You have confused me. I started to use Debian about 4 months ago > because I no longer want to build and update my custom

Re: Domain name to use on home networks

Sent from my iPadOn Oct 27, 2023, at 10:00 AM, Andrew M.A. Cater wrote:On Fri, Oct 27, 2023 at 09:30:09AM -0400, Pocket wrote:Sent from my iPadOn Oct 27, 2023, at 9:05 AM, Greg Wooledge wrote:On Fri, Oct 27, 2023 at 07:59:00AM -0400, Pocket wrote:On 10/27/23 07:50, Greg Wooledge wrote:On Fri,

Re: Domain name to use on home networks

On Fri, Oct 27, 2023 at 09:30:09AM -0400, Pocket wrote: > > > Sent from my iPad > > > On Oct 27, 2023, at 9:05 AM, Greg Wooledge wrote: > > > > On Fri, Oct 27, 2023 at 07:59:00AM -0400, Pocket wrote: > >>> On 10/27/23 07:50, Greg Wooledge wrote: > >>> On Fri, Oct 27, 2023 at 07:29:20AM

Re: Domain name to use on home networks

Sent from my iPad > On Oct 27, 2023, at 9:05 AM, Greg Wooledge wrote: > > On Fri, Oct 27, 2023 at 07:59:00AM -0400, Pocket wrote: >>> On 10/27/23 07:50, Greg Wooledge wrote: >>> On Fri, Oct 27, 2023 at 07:29:20AM -0400, Pocket wrote: /etc/hosts >>> If you're using short-form hostnames

Re: Domain name to use on home networks

On Fri, Oct 27, 2023 at 07:59:00AM -0400, Pocket wrote: > On 10/27/23 07:50, Greg Wooledge wrote: > > On Fri, Oct 27, 2023 at 07:29:20AM -0400, Pocket wrote: > > > /etc/hosts > > If you're using short-form hostnames like this: > > > > unicorn:~$ hostname > > unicorn > > > > then yeah, that's all

Re: Domain name to use on home networks

On 10/27/23 07:50, Greg Wooledge wrote: On Fri, Oct 27, 2023 at 07:29:20AM -0400, Pocket wrote: On 10/27/23 07:12, gene heskett wrote: I tried to change just this machine to see how its done, and managed to get all the right answers, which did not affect my local network since I generally

Re: Domain name to use on home networks

On Fri, Oct 27, 2023 at 07:29:20AM -0400, Pocket wrote: > On 10/27/23 07:12, gene heskett wrote: > > I tried to change just this machine to see how its done, and managed to > > get all the right answers, which did not affect my local network since I > > generally use the alias name for an ssh or

Re: Domain name to use on home networks

On 10/27/23 07:12, gene heskett wrote: On 10/27/23 00:47, Stefan Monnier wrote: I would have thought that techies understand its origins, and non-techies are fairly unlikely ever to encounter it. That's the thing: if you use `home.arpa` for your home network, suddenly it's exposed to

Re: Domain name to use on home networks

On 10/27/23 00:47, Stefan Monnier wrote: I would have thought that techies understand its origins, and non-techies are fairly unlikely ever to encounter it. That's the thing: if you use `home.arpa` for your home network, suddenly it's exposed to non-techies, like your friends and family,

Re: Domain name to use on home networks

On 27 Oct 2023 00:46 -0400, from monn...@iro.umontreal.ca (Stefan Monnier): >> I would have thought that techies understand its origins, and >> non-techies are fairly unlikely ever to encounter it. > > That's the thing: if you use `home.arpa` for your home network, suddenly > it's exposed to

Re: Domain name to use on home networks

> I would have thought that techies understand its origins, and > non-techies are fairly unlikely ever to encounter it. That's the thing: if you use `home.arpa` for your home network, suddenly it's exposed to non-techies, like your friends and family, contrary to things like `in-addr.arpa`.

Re: Domain name to use on home networks; was: Bookworm:NetworkManager

On Thu 26 Oct 2023 at 07:58:45 (+0800), jeremy ardley wrote: > On 26/10/23 07:24, David Wright wrote: > > > Or if you already have a domain, you can use a subdomain. eg. I have > > > rail.eu.org, and at home it is depot.rail.eu.org > > I'm not sure how that would work when my home network > > is

Re: Domain name to use on home networks

On Wed 25 Oct 2023 at 22:42:07 (-0400), Stefan Monnier wrote: > >> It's just such a shame that they chose a name which refers to "arpa" > >> in it, which is not only US-centric but even belongs to the US's war > >> department, which I find rather unpalatable. > >> I understand ARPA was closely

Re: Domain name to use on home networks

On 26 Oct 2023 05:07 -0400, from noloa...@gmail.com (Jeffrey Walton): > I think the real unpalatable part of DNS is, most of the operators are > US-based: Nothing about home.arpa requires or relies on the use of DNS, and most residential networks are probably small enough that a non-DNS setup

Re: Domain name to use on home networks

On 26 Oct 2023 10:33 +0200, from m...@dorfdsl.de (Marco M.): >> Certainly "local." would have been one possibility, but that is >> reserved _specifically_ for mDNS (RFC 6762) although is often >> incorrectly used for non-mDNS names. > > rfc6762 >From section 3 of that RFC: > This document

Re: Domain name to use on home networks

Am 26.10.2023 um 08:16:47 Uhr schrieb Michael Kjörling: > Certainly "local." would have been one possibility, but that is > reserved _specifically_ for mDNS (RFC 6762) although is often > incorrectly used for non-mDNS names. rfc6762 |Implementers MAY choose to look up such names concurrently

Re: Domain name to use on home networks

Am 25.10.2023 um 21:23:41 Uhr schrieb Stefan Monnier: > I understand ARPA was closely related to the beginnings of the > Internet, but... couldn't they choose something a bit more neutral? I don't know the exact reason for that decision, but I assume they used it because it is already there,

Re: Domain name to use on home networks

On 25 Oct 2023 21:23 -0400, from monn...@iro.umontreal.ca (Stefan Monnier): >> If you go with the domain name home.arpa and an IPv4 subnet sliced out >> of one of 192.168.0.0/16, 172.12.0.0/12 or 10.0.0.0/8, you can be >> _almost certain_ that nothing will break because of those choices, now >>

Re: Domain name to use on home networks

>> It's just such a shame that they chose a name which refers to "arpa" >> in it, which is not only US-centric but even belongs to the US's war >> department > > It belongs to the Internet Architecture Board and is administered by > IANA which is why they chose it. It stands for "Address and

Re: Domain name to use on home networks

Stefan writes: > It's just such a shame that they chose a name which refers to "arpa" > in it, which is not only US-centric but even belongs to the US's war > department It belongs to the Internet Architecture Board and is administered by IANA which is why they chose it. It stands for "Address

Re: Domain name to use on home networks

> If you go with the domain name home.arpa and an IPv4 subnet sliced out > of one of 192.168.0.0/16, 172.12.0.0/12 or 10.0.0.0/8, you can be > _almost certain_ that nothing will break because of those choices, now > _or_ in the future. 100% agreement. It's just such a shame that they chose a

Re: Domain name to use on home networks; was: Bookworm:NetworkManager

On Oct 26, 2023, jeremy ardley wrote: > > On 26/10/23 07:24, David Wright wrote: > > > Or if you already have a domain, you can use a subdomain. eg. I have > > > rail.eu.org, and at home it is depot.rail.eu.org > > I'm not sure how that would work when my home network > > is on a different

Re: Domain name to use on home networks; was: Bookworm:NetworkManager

On 26/10/23 07:24, David Wright wrote: Or if you already have a domain, you can use a subdomain. eg. I have rail.eu.org, and at home it is depot.rail.eu.org I'm not sure how that would work when my home network is on a different continent from my domain's hosting. This is no problem asides

Re: Domain name to use on home networks; was: Bookworm:NetworkManager

On Wed 25 Oct 2023 at 08:33:25 (+0200), Erwan David wrote: > Le 25/10/2023 à 03:47, David Wright a écrit : > > On Mon 23 Oct 2023 at 12:06:05 (+0200), Christian Groessler wrote: > > > On 10/23/23 07:29, Jeffrey Walton wrote: > > > > On Mon, Oct 23, 2023 at 1:24 AM ghe2001 wrote: > > > > > How

  1   2   >