3 ms·
I disagree after seeing what happened with .dev. I myself was concerned about it but it turned out to be fine. This will be the same.
by benatkin 3y ago
I disagree after seeing what happened with .dev. I myself was concerned about it but it turned out to be fine. This will be the same.
- skrebbel 3y agoBecause .dev is such a common filename extension?
- benatkin 3y agoI'm not seeing the attack vector. The URL of this page certainly doesn't show it.
- SpaghettiCthulu 3y agoProbably because it's a reasonable TLD to use internally for testing
- Spivak 3y agoWhy are you getting downvoted, that's literally what happened when it launched. A bunch of people were like shit I use .dev internally. Nobody used .test, .example, or .home.arpa
- justin_oaks 3y agoYup. It happened to me. After the .dev TLD was created, I switched all my internal dev hostnames over to .test because it's one of the reserved TLDs [1]. I also switched off of .local after learning that it's used for mDNS [2]. 1: https://www.rfc-editor.org/rfc/rfc2606.html#page-2 https://www.rfc-editor.org/rfc/rfc2606.html#page-2 2: https://en.wikipedia.org/wiki/.local https://en.wikipedia.org/wiki/.local
- CydeWeys 3y agoExcept that it's not, and never was, because it was never expressly reserved for this purpose. And it was particularly unreasonable to use for testing since 2012 when multiple applications were submitted to ICANN to create it as a gTLD.
- Nicksil 3y agoWhat was your concern with .dev?
- benatkin 3y agoA) Prior use - this is why I think zip won't be a big deal, people will adapt. B) Being a good domain name for development - mysite.localhost turned out to be better.
- Taywee 3y agomysite.localhost works fine for very simple development, but can easily fall down with containers, VMs, or multi-machine development. Technically, you can point it to a non-loopback IP, but I wouldn't do that. .localdomain is used some places as well, but I don't know how reliable it is. .test is a bit more flexible, and what I use now. I'd prefer if .dev was reserved as well, but that ship has sailed.
- benatkin 3y agoIt sure can because browsers resolve .localhost https://datatracker.ietf.org/doc/html/draft-west-let-localhost-be-localhost-06 https://datatracker.ietf.org/doc/html/draft-west-let-localho... Indeed the ship has sailed and you can use anything now. I'm in favor of .test becoming a gTLD so you might want to get off that.
- CydeWeys 3y ago.test will not become a gTLD. See RFC 2606.
- benatkin 3y agoAs gTLDs increase in popularity they could amend that RFC. Also it's not particularly clear and unchanging already. "TLDs for Testing, & Documentation Examples" includes .localhost. However, .localhost can be used for more than just testing and documentation. It's treated as a secure context in browsers and subdomains have different storage areas on browsers. (Shockingly, localhost:8000 and localhost:8080 aren't kept separate by browsers)
- organsnyder 3y agoI use my .dev domain as my email address. I've encountered a couple of systems that refuse to accept it, I'm assuming because it's what they use for internal testing (though it's also possible that their validation algorithms just assume a narrow range of TLDs).
- benatkin 3y agoThat's on them. RFCs are free to view and download.
- organsnyder 3y agoOh, absolutely. But that doesn't mean it doesn't inconvenience me as well.