Closed celkins closed 10 years ago
Namespacing is important. How about appending localhost to the project name: foo.localhost
That's what I was suggesting: localhost
as domain name (cf. http://tools.ietf.org/html/rfc6761#section-6.3).
:+1:
To safely satisfy these needs, four domain names are reserved as listed and described below.
.test .example .invalid .localhost ".test" is recommended for use in testing of current or new DNS related code. ".example" is recommended for use in documentation or as examples. ".invalid" is intended for use in online construction of domain names that are sure to be invalid and which it is obvious at a glance are invalid. The ".localhost" TLD has traditionally been statically defined in host DNS implementations as having an A record pointing to the loop back IP address and is reserved for such use. Any other use would conflict with widely deployed code which assumes this use.
I don't think that restricting this module to .localhost
is the right approach. Even though today we resolve to 127.0.0.1, I'd prefer to default to something which doesn't imply local loopback. .test
is short, meant for testing work, and is reserved for this kind of use.
In any case, this TLD should be configurable; I don't want to push this change without a way for organizations to keep their old configuration.
Thanks to @tmcinerney in #12, the TLD is configurable using hiera. We're still defaulting to .dev
, but if you're ready to change to another TLD, you can.
Both Amazon and Google have applied for the
dev
TLD. Given that one of those applications may be approved and that using an unreserved domain name is bad form anyway, it would be wise to switch to a reserved domain name. It may not be pretty, butlocalhost
is arguably the most appropriate.