On Fri, 26 Feb 2016, Craig Skinner wrote:
You could have a monthly email to remind you to check if it is
registered. If that _EVER_ happens, you can easily change a small
network to .priv (or something else) on a lazy wet afternoon. No drama.
For a hobbyist network, it doesn't matter too much
Hi Rodrigo,
On 2016-02-25 Thu 15:18 PM |, Roderick wrote:
>
> My names without dots in /etc/hosts are to be considered as names
> immediately under the root in the DNS tree, as also "localhost"
> (localhost.). The names inflation has a bad effect on my praxis.
> Is/was it not a common praxis? Som
On Wed, 24 Feb 2016, Janne Johansson wrote:
Since "dk." resolves to an A-record, I guess that works as an FQDN.
We tend to suppose that a FQDN is a hostname plus a domain, but this
is obviously not the case. Any string as described at the end of
hosts (5) should serve as a host name.
We conti
Hello anyone and thanks for the clarifications!
On Thu, 25 Feb 2016, Craig Skinner wrote:
Here's the full public domain name root list (which changes):
http://www.iana.org/domains/root/db
There is an inflation of TLD Names. I hope that registering a
domain name become cheaper due to this abun
On Thu, 25 Feb 2016, Stuart Henderson wrote:
> On 2016-02-24, Kamil Cholewiński wrote:
>> This. See how Google bought '.dev'.
>>
>> https://tools.ietf.org/html/rfc2606
>
> was cheaper to buy the TLD to prevent anyone else from grabbing
> it, rather than change it>
Definitely. At Google's scale,
On 2016-02-24, Kamil Cholewiński wrote:
> On Wed, 24 Feb 2016, Peter Hessler wrote:
>> On 2016 Feb 24 (Wed) at 12:59:04 + (+), Craig Skinner wrote:
>> :Hi Rodrigo,
>> :
>> :On 2016-02-24 Wed 10:48 AM |, Roderick wrote:
>> :>
>> :> Should the name in /etc/myname include a domain name? Eve
On 2016-02-24 Wed 14:13 PM |, Kamil Cholewi??ski wrote:
>
> Any other relevant RFC's?
>
Yes Kamil;-
RFC 6761 (2606) reserves
*) .example: for use in examples, includes .example.{com,net,org}
*) .invalid: for use as obviously invalid
(@address.invalid has special meaning for M
On Wed, Feb 24, 2016 at 12:59:04PM +, Craig Skinner wrote:
> Do not use .local - it buggers up Apple toys.
I would also recommend not using any valid top-level domain that you do not
control for
this purpose.
A certain (microsoft-heavy) organization's choice of $companyname.int as the
domai
On Wed, 24 Feb 2016, Peter Hessler wrote:
> On 2016 Feb 24 (Wed) at 12:59:04 + (+), Craig Skinner wrote:
> :Hi Rodrigo,
> :
> :On 2016-02-24 Wed 10:48 AM |, Roderick wrote:
> :>
> :> Should the name in /etc/myname include a domain name? Even when I
> :> do not have a static IP registered
On 2016 Feb 24 (Wed) at 12:59:04 + (+), Craig Skinner wrote:
:Hi Rodrigo,
:
:On 2016-02-24 Wed 10:48 AM |, Roderick wrote:
:>
:> Should the name in /etc/myname include a domain name? Even when I
:> do not have a static IP registered in a public DNS?
:>
:
:Yes, these non-public "domains" a
Hi Rodrigo,
On 2016-02-24 Wed 10:48 AM |, Roderick wrote:
>
> Should the name in /etc/myname include a domain name? Even when I
> do not have a static IP registered in a public DNS?
>
Yes, these non-public "domains" are suitable:
.localdomain
.internal
.private
.priv
You can serve them on your
2016-02-24 11:48 GMT+01:00 Roderick :
> Dear Sirs!
>
> Should the name in /etc/myname include a domain name? Even when I
> do not have a static IP registered in a public DNS?
>
> In "man 5 myname" I read:
>
> "The file should contain a single line specifying the fully
> qualified domain name (FQDN
Dear Sirs!
Should the name in /etc/myname include a domain name? Even when I
do not have a static IP registered in a public DNS?
In "man 5 myname" I read:
"The file should contain a single line specifying the fully
qualified domain name (FQDN) of the system"
Does FQDN mean, that anyone in the
13 matches
Mail list logo
