id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc
742	We are not using correct domain name examples, as per RFC 2606	lizardo@…	lfs-book@…	"See http://www.faqs.org/rfcs/rfc2606

On ""Creating the /etc/hosts file"" section (Chapter 7), we use example /etc/host
files and ask the user to change the dummy values with the correct ones. RFC
2606 recommends that, when writing documentation which uses dummy domain names
as example, we use one of the following reserved domains:

example.com
example.net
example.org

The main reason is that ""Confusion and conflict can be caused by the use of a
current or future top level domain name in experimentation or testing, as an
example in documentation,to indicate invalid names, or as a synonym for the loop
back address.""

Additionally, the same RFC describes the use of "".localhost"" as loopback
reserved TLD, but does not mention "".localdomain"" anywhere. Although common in
many network configuration files, the .localdomain TLD does not seem to be
reserved for loopback purposes. For example, most of the ICANN mailing list
messages (see http://www.google.com/search?q=localhost+site%3Aicann.org) show
""localhost"" being used as loopback TLD with a few occurrences (exact four) of
the ""localhost.localdomain"" address.

In resume, my suggestions are:

- Substitute ""mydomain.org"" and ""mydomain.com"" with the proper ""example.org"" value;

- Substitute ""localhost.localdomain"" with ""localdomain.localhost"", IF this
change does not break anything."	defect	closed	lowest		Book	CVS	normal	fixed