From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Choice of TLD for internal network
Date: Tue, 19 Dec 2017 17:00:33 +0000 [thread overview]
Message-ID: <6971819.42xP9Zg8s3@peak> (raw)
In-Reply-To: <5A3940D6.5080907@youngman.org.uk>
On Tuesday, 19 December 2017 16:39:50 GMT Wols Lists wrote:
> On 19/12/17 13:57, Michael Orlitzky wrote:
> > There are no safe, free names to use for an internal network. On the one
> > hand, RFC 8244 makes a decent argument that this is a good thing,
> > because it guarantees that every hostname is globally unique (so if I
> > copy/paste a URL to you, it goes the same place on your machine as it
> > did mine). On the other hand, I hate the idea of paying some bureaucrat
> > to be able to use my own network.
>
> Which was why I liked Demon as my ISP. They had a customer domain and
> assigned you a name on it. Whether you used it as a host or domain name
> was up to you.
>
> Most ISPs now assume you are a client and don't give you proper internet
> :-(
Zen is fine too. I had to choose a subdomain (prh) in myzen.co.uk, then I
could define 11 users@prh.myzen.co.uk. I've only used a few of those, as any
user names local to my LAN aren't supposed to be visible outside it.
Any time I look round for a new ISP to change to for any reason, I'm only
ever interested in those that act as a pair of bare wires connecting me and
mine to the outside world - no interference,* no proxies, transparent or
otherwise. Just a simple connection.
I forget why I left Demon years ago. I wouldn't touch BT Internet with a
barge-pole since they got all cosy with Yahoo, and UKFSN went more-or-less
defunct. Whence Zen today.
* [OT] What's the difference between intervention and interference? None
that I can see. One is just more Politically Crass - oops! Correct - than
the other.
--
Regards,
Peter.
next prev parent reply other threads:[~2017-12-19 17:00 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 2:05 [gentoo-user] Choice of TLD for internal network Peter Humphrey
2017-12-18 2:11 ` R0b0t1
2017-12-18 9:49 ` Adam Carter
2017-12-18 10:45 ` Peter Humphrey
2017-12-18 10:57 ` Neil Bothwick
2017-12-20 2:23 ` Peter Humphrey
2017-12-18 14:37 ` R0b0t1
2017-12-19 0:10 ` Peter Humphrey
2017-12-19 0:41 ` Adam Carter
2017-12-19 2:06 ` [gentoo-user] " Ian Zimmerman
2017-12-19 3:19 ` R0b0t1
2017-12-18 13:56 ` [gentoo-user] " Michael Orlitzky
2017-12-18 14:31 ` Peter Humphrey
2017-12-18 14:34 ` Michael Orlitzky
2017-12-18 19:19 ` David Haller
2017-12-18 19:55 ` Wol's lists
2017-12-18 20:08 ` Michael Orlitzky
2017-12-18 20:25 ` David Haller
2017-12-18 21:58 ` Bill Kenworthy
2017-12-19 13:59 ` Michael Orlitzky
2017-12-19 14:40 ` Neil Bothwick
2017-12-19 13:57 ` Michael Orlitzky
2017-12-19 16:39 ` Wols Lists
2017-12-19 17:00 ` Peter Humphrey [this message]
2017-12-19 20:31 ` Neil Bothwick
2017-12-20 0:33 ` Peter Humphrey
2017-12-20 1:09 ` Neil Bothwick
2017-12-20 2:12 ` Peter Humphrey
2017-12-20 14:22 ` Wols Lists
2017-12-20 4:03 ` Adam Carter
2017-12-19 17:22 ` R0b0t1
2017-12-19 17:58 ` Michael Orlitzky
2017-12-19 18:22 ` R0b0t1
2017-12-19 17:28 ` [gentoo-user] " Ian Zimmerman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6971819.42xP9Zg8s3@peak \
--to=peter@prh.myzen.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox