3 ms·

It seems like using .dev TLD is a bad idea since Google owns it[1]. How many people use the .dev or .local TLD? What's the best practice here? [1] https://www.

It seems like using .dev TLD is a bad idea since Google owns it[1]. How many people use the .dev or .local TLD? What's the best practice here? [1] https://www.iana.org/domains/root/db/dev.html https://www.iana.org/domains/root/db/dev.html

icebraining 11y ago
.local is actually reserved for such purpose: https://en.wikipedia.org/wiki/.local https://en.wikipedia.org/wiki/.local
- silvamerica 11y ago
  It seems to me that .local is reserved for purposes within a local network, not necessarily local to an individual computer itself. You could, for example, set up an internal server on your network and have it resolve with storage.local. You could argue that a collection of containers is basically the same thing, though.
  - icebraining 11y ago
    If a container has its own IP address, I think it can be considered its own device on the network, regardless of the details.
- josegonzalez 11y ago
  OS X does weird stuff with the .local tld, making usage of it for local hosts non-trivial. https://support.apple.com/en-us/HT201275 https://support.apple.com/en-us/HT201275
  - e12e 11y ago
    Not, that weird: > Host names that contain only one label in > addition to local, for example > "My-Computer.local", are resolved using > Multicast DNS (Bonjour) by default. Host names > that contain two or more labels in addition to > local, for example "server.domain.local", are > resolved using a DNS server by default. Apparently there's nothing wrong with adapting, say, .dev.local (or .ifft.local) with a coresponding hack, ahem, file, under /etc/resolver/dev.local: http://blog.scottlowe.org/2006/01/04/mac-os-x-and-local-domains/ http://blog.scottlowe.org/2006/01/04/mac-os-x-and-local-doma...
    - silvamerica 11y ago
      That looks like a great way to handle it!
silvamerica 11y ago
That's a fair point. I had been using .dev for this purpose for years, and just applied it to this project out of habit. It still doesn't fully resolve to anything from Google, but I see that ICANN is now resolving it to 127.0.53.53 to indicate a name collision. Many other projects (like Boxen) also use .dev, so it seems to still be something that people do.
tdkl 11y ago
Using anything beside a domain you own and control is a potential bad idea.

icebraining 11y ago

.local is actually reserved for such purpose: https://en.wikipedia.org/wiki/.local https://en.wikipedia.org/wiki/.local

silvamerica 11y ago
It seems to me that .local is reserved for purposes within a local network, not necessarily local to an individual computer itself. You could, for example, set up an internal server on your network and have it resolve with storage.local. You could argue that a collection of containers is basically the same thing, though.
- icebraining 11y ago
  If a container has its own IP address, I think it can be considered its own device on the network, regardless of the details.
josegonzalez 11y ago
OS X does weird stuff with the .local tld, making usage of it for local hosts non-trivial. https://support.apple.com/en-us/HT201275 https://support.apple.com/en-us/HT201275
- e12e 11y ago
  Not, that weird: > Host names that contain only one label in > addition to local, for example > "My-Computer.local", are resolved using > Multicast DNS (Bonjour) by default. Host names > that contain two or more labels in addition to > local, for example "server.domain.local", are > resolved using a DNS server by default. Apparently there's nothing wrong with adapting, say, .dev.local (or .ifft.local) with a coresponding hack, ahem, file, under /etc/resolver/dev.local: http://blog.scottlowe.org/2006/01/04/mac-os-x-and-local-domains/ http://blog.scottlowe.org/2006/01/04/mac-os-x-and-local-doma...
  - silvamerica 11y ago
    That looks like a great way to handle it!

silvamerica 11y ago

That's a fair point. I had been using .dev for this purpose for years, and just applied it to this project out of habit. It still doesn't fully resolve to anything from Google, but I see that ICANN is now resolving it to 127.0.53.53 to indicate a name collision. Many other projects (like Boxen) also use .dev, so it seems to still be something that people do.

tdkl 11y ago

Using anything beside a domain you own and control is a potential bad idea.