[alfs-log] [ALFS Trac] #1707: Do not use lfs.org as a domain name

ALFS Trac trac at linuxfromscratch.org
Mon Apr 10 06:06:09 PDT 2017


#1707: Do not use lfs.org as a domain name
--------------------+-----------------------
 Reporter:  pierre  |       Owner:  pierre
     Type:  defect  |      Status:  assigned
 Priority:  high    |   Milestone:  2.4.1
Component:  jhalfs  |     Version:  2.4
 Severity:  normal  |  Resolution:
 Keywords:          |
--------------------+-----------------------

Comment (by pierre):

 Using something illegal (!**EDITME for example) and testing it in jhalfs
 is not fair to users, because it is in a submenu the user may just not
 open and not see... In this [https://www.howtogeek.com/167190/how-and-why-
 to-assign-the-.local-domain-to-your-raspberry-pi/ HowTo], you can find
 some reasons to use "local". Roughly, if avahi is present on the machine
 with a full name of the form ''hostname.local'', it can be found by name
 on the local network, instead of by address. OTOH, that may be a bad
 choice for some other configurations see [http://www.mdmarra.com/2012/11
 /why-you-shouldnt-use-local-in-your.html this blog]. The use of "local" is
 defined in [https://tools.ietf.org/html/rfc6762 RFC 6762]. Here is a
 extract:
    However, the majority of home computer users do not
    have easy access to any portion of the global DNS namespace within
    which they have the authority to create names.  This leaves the
    majority of home computers effectively anonymous for practical
    purposes.
    To remedy this problem, this document allows any computer user to
    elect to give their computers link-local Multicast DNS host names of
    the form: "single-dns-label.local.".  For example, a laptop computer
    may answer to the name "!MyComputer.local.".  Any computer user is
    granted the authority to name their computer this way, provided that
    the chosen host name is not already in use on that link.  Having
    named their computer this way, the user has the authority to continue
    utilizing that name until such time as a name conflict occurs on the
    link that is not resolved in the user's favor. [...]

 Now, as long as the local network is isolated from global internet, and
 specially from outside DNS, you can use any domain name. This is the case
 if using the network stack from qemu, as the other default addresses
 suggest. So why bother?

 Well, advising users to use registered domain names might not be a good
 idea, if they happen to misconfigure their DNS... Names which are
 guaranteed to work on local networks and to be harmless on global internet
 are example{,.com,.net,.org}. See [https://tools.ietf.org/html/rfc6761 RFC
 6761] But they normally are reserved for documentation.

 Another possibility is to use .test names
 ([https://tools.ietf.org/html/rfc6761 RFC 6761]). They should not be
 recognized as special by softwares, but are recognized as non existent by
 caching DNS and root DNS.

 All in all, I think "local" default is the most adapted for what we think
 users will do. Otherwise, "lfs.test" might be not too bad. Comments?

--
Ticket URL: <http://wiki.linuxfromscratch.org/alfs/ticket/1707#comment:3>
ALFS Trac <http://wiki.linuxfromscratch.org/alfs/>
Automated Linux From Scratch


More information about the alfs-log mailing list