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

2023-10-26 Thread David Wright
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; was: Bookworm:NetworkManager

2023-10-25 Thread Dan Purgert
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

2023-10-25 Thread jeremy ardley
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

2023-10-25 Thread David Wright
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

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

2023-10-25 Thread Erwan David
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 about a /29 or so, named "here.", hosts named 2 or 3 letter abbreviations of what you

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

2023-10-24 Thread Marco M.
Am 25.10.2023 um 03:40:46 Uhr schrieb ghe2001: > TLD '.lan' works. As best I can tell on the web, it doesn't exist. Is it intended for that? No? Then don't use it. It can be used in the future for public domains.

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

2023-10-24 Thread ghe2001
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 --- Original Message --- On Tuesday, October 24th, 2023 at 7:47 PM, David Wright wrote: > On Mon 23 Oct 2023 at 12:06:05 (+0200), Christian Groessler wrote: > > > On 10/23/23 07:29, Jeffrey Walton wrote: > > > > Just register a

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

2023-10-24 Thread David Wright
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 about a /29 or so, named "here.", hosts named 2 or 3 > > > letter abbreviations of what you call the computers, with

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

2023-10-23 Thread gene heskett
On 10/23/23 16:35, Andy Smith wrote: Hello, On Sun, Oct 22, 2023 at 10:33:47PM -0400, gene heskett wrote: On 10/22/23 20:48, Greg Wooledge wrote: Any issues you've encountered have been the result of misconfiguration. You have repeatedly shown errors in your config files, and once those have

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

2023-10-23 Thread gene heskett
On 10/23/23 14:09, Greg Wooledge wrote: On Mon, Oct 23, 2023 at 12:12:50PM -0400, gene heskett wrote: Google seems to have high jacked port 80 https://lists.debian.org/msgid-search/0a8b96aa-8630-ee5c-5135-59221c55b...@shentel.net They have, chromium, the google browser, absolutely cannot be

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

2023-10-23 Thread Andy Smith
Hello, On Sun, Oct 22, 2023 at 10:33:47PM -0400, gene heskett wrote: > On 10/22/23 20:48, Greg Wooledge wrote: > > Any issues you've encountered have been the result of misconfiguration. > > You have repeatedly shown errors in your config files, and once those > > have been corrected, everything

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

2023-10-23 Thread Andrew M.A. Cater
On Mon, Oct 23, 2023 at 02:09:31PM -0400, Greg Wooledge wrote: > On Mon, Oct 23, 2023 at 12:12:50PM -0400, gene heskett wrote: > > > > Google seems to have high jacked port 80 > > > > > > https://lists.debian.org/msgid-search/0a8b96aa-8630-ee5c-5135-59221c55b...@shentel.net > > > > > They have,

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

2023-10-23 Thread Greg Wooledge
On Mon, Oct 23, 2023 at 12:12:50PM -0400, gene heskett wrote: > > > Google seems to have high jacked port 80 > > > > https://lists.debian.org/msgid-search/0a8b96aa-8630-ee5c-5135-59221c55b...@shentel.net > > > They have, chromium, the google browser, absolutely cannot be sent to >

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

2023-10-23 Thread gene heskett
On 10/22/23 22:55, Max Nikulin wrote: On 23/10/2023 04:43, gene heskett wrote: As I keep repeating Dan, there is not a local dns, its all a 15 entry hosts file atm. So that cannot bite /me/. It can. Some day .den TLD may be registered and chosen by a 3d printer manufacturer. It might

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

2023-10-23 Thread ghe2001
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 --- Original Message --- On Sunday, October 22nd, 2023 at 11:29 PM, Jeffrey Walton wrote: > Whatever you come up with for , ICANN can add to the > > gTLD namespace; see https://icannwiki.org/Brand_TLD. > > > The DNS queries for

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

2023-10-23 Thread gene heskett
On 10/22/23 22:37, John Hasler wrote: Gene writes: This is generally true, Greg, and I get that, but every new version, which should just continue what works, doesn't cuz somebody moved a config file and last years fix doesn't work this year. And you can't ask for help when its not working. So

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

2023-10-23 Thread gene heskett
On 10/22/23 23:08, Stefan Monnier wrote: This is generally true, Greg, and I get that, but every new version, which should just continue what works, doesn't cuz somebody moved a config file and last years fix doesn't work this year. And you can't ask for help when its not working. So YOU have

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

2023-10-23 Thread Christian Groessler
On 10/23/23 07:29, Jeffrey Walton wrote: On Mon, Oct 23, 2023 at 1:24 AM ghe2001 wrote: How about a /29 or so, named "here.", hosts named 2 or 3 letter abbreviations of what you call the computers, with unroutable IPs, DNS'ed in /etc/hosts (with shortcuts). Whatever you come up with for ,

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

2023-10-23 Thread Max Nikulin
On 23/10/2023 09:59, Stefan Monnier wrote: I can relate to Gene's feelings since there's been indeed some churn over the years, but `/etc/hosts` seems like an odd example because this one is among the most stable part of Unix/Linux. Gene's issue was with resolv.conf and he was refusing Greg's

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

2023-10-22 Thread Jeffrey Walton
On Mon, Oct 23, 2023 at 1:24 AM ghe2001 wrote: > > How about a /29 or so, named "here.", hosts named 2 or 3 > letter abbreviations of what you call the computers, with unroutable IPs, > DNS'ed in /etc/hosts (with shortcuts). Whatever you come up with for , ICANN can add to the gTLD namespace;

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

2023-10-22 Thread Stefan Monnier
>> This is generally true, Greg, and I get that, but every new version, >> which should just continue what works, doesn't cuz somebody moved a >> config file and last years fix doesn't work this year. And you can't >> ask for help when its not working. So YOU have to fix it based of what >> YOU

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

2023-10-22 Thread Max Nikulin
On 23/10/2023 04:43, gene heskett wrote: As I keep repeating Dan, there is not a local dns, its all a 15 entry hosts file atm. So that cannot bite /me/. It can. Some day .den TLD may be registered and chosen by a 3d printer manufacturer. It might happen that you would not be able to access

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

2023-10-22 Thread John Hasler
Gene writes: > This is generally true, Greg, and I get that, but every new version, > which should just continue what works, doesn't cuz somebody moved a > config file and last years fix doesn't work this year. And you can't > ask for help when its not working. So YOU have to fix it based of what

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

2023-10-22 Thread gene heskett
On 10/22/23 20:48, Greg Wooledge wrote: On Sun, Oct 22, 2023 at 08:36:53PM -0400, gene heskett wrote: What really bugs me is when the maintainers forget there are hosts file users, and do something that totally screws us up, Gene, you're being irrational again. "Hosts file only" systems have

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

2023-10-22 Thread ghe2001
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 How about a /29 or so, named "here.", hosts named 2 or 3 letter abbreviations of what you call the computers, with unroutable IPs, DNS'ed in /etc/hosts (with shortcuts). Works here... -- Glenn English -BEGIN PGP SIGNATURE- Version:

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

2023-10-22 Thread gene heskett
On 10/22/23 14:17, Dan Ritter wrote: gene heskett wrote: On 10/22/23 11:19, Jeffrey Walton wrote: On Sun, Oct 22, 2023 at 7:13 AM Michael Kjörling <2695bd53d...@ewoof.net> wrote: https://www.rfc-editor.org/info/rfc8375 Chuckle. Looks like a solution looking for a problem. You can use