Re: domain names, was: hostname
On Mon 19 Feb 2018 at 20:30:28 +0000, Joe wrote:
> On Mon, 19 Feb 2018 19:28:55 +0000
> Brian <ad44@cityscape.co.uk> wrote:
>
> > On Mon 19 Feb 2018 at 19:08:42 +0000, Brad Rogers wrote:
> >
> > > On Mon, 19 Feb 2018 18:58:25 +0000
> > > Brian <ad44@cityscape.co.uk> wrote:
> > >
> > > Hello Brian,
> > >
> > > >Avoiding using any of the examples you give is also recommended
> > > >because you do not own the domain name google.com and have no
> > > >right to use it.
> > >
> > > I took that as a given.
> > >
> > > Still, it's probably as well to point it out because you never know;
> > > some buffoon may think it's clever or (forgive me for this) 'kewl'
> > > to do so.
> >
> > Could be inadvertent. ilovecats.com or scratchyouritch.com or
> > deeppockets.com look good and safe when you are installing.
> > microsoft20.com (but not google20.com) is ok until someone
> > registers it.
> >
> > The best thing is to leave the domain name field blank unless
> > you *know* you need one. I do not think either the installer
> > or the documentation put it like this.
> >
>
> It is somewhat safer to use a non-existent top level domain, though
> less so that it used to be. I would think '.invalid' ought to remain
> safe, but you never can tell what fools will do.
.invalid should fit the bill. You don't get much help on this from the
installer in expert mode though. My point was - how do you know what is
non-existent? knickersoff.com was a revelation to me!
Leave (or make) it blank should be the advice for most users; it is of
no importance and (I suspect) only confuses them.
--
Brian.
Reply to: