Earlier quoted context omitted.
> ".test" is recommended for use in testing of current or new DNS related code. This one looks the safest and least prone to confusion. > ".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. Both of these look problematic from a terminology standpoint, not…
.test is also problematic for the purpose of hosting internal (but not development/testing) domains on a private network. There is a draft RFC to reserve .internal for this purpose, which I think makes a lot of sense. https://github.com/wkumari/draft-wkumari-dnsop-internal
Google .dev domain early access
431–440 of 475 posts
Re: Google .dev domain early access
#432Earlier quoted context omitted.
Who bought it is irrelevant. It could have been released to the public in a similar way to .com and the same issue would remain. The .dev TLD was never reserved for your dev use. If you had been doing it correctly and following the RFC, you wouldn’t have to change anything with your workflow. Now, if they ever release .test for public use then I’ll grab my pitchfork with you.
Thankfully RFC 2606 ensures that that will never happen.
Re: Google .dev domain early access
#433The .dev TLD worked fine before it was bought. Now we have to use .test or .local. I don't get what Google thinks they'll get out of sponsoring putting sites under development online.
> .dev will operate as a closed gTLD. It will provide Google with the opportunity to differentiate and innovate upon its Google products and services through its use of the gTLD. This will promote competition in the gTLD space by inciting competitors to respond with improved gTLD operations, greater range and higher quality products and services, and⁄or the creation of their own respective gTLDs, to the benefit of all Internet users. Launching the proposed gTLD will also generate increased competition in the online marketplace by adding incremental availability to the second-level domain pool.
[0]: https://gtldresult.icann.org/applicationstatus/applicationde...
Re: Google .dev domain early access
#434All of those new gTLDs are pure racketeering. Sub-domains worked fine (and still do!) for testing or development purposes. Or even company-dev.com I fail to see what value there is in a .dev tld.
> I fail to see what value there is in a .dev tld. Then don't buy one?
Yet, Internet companies (like Google) who participate in this should lose a little respect from everyone.
Re: Google .dev domain early access
#435Earlier quoted context omitted.
.test is also problematic for the purpose of hosting internal (but not development/testing) domains on a private network. There is a draft RFC to reserve .internal for this purpose, which I think makes a lot of sense. https://github.com/wkumari/draft-wkumari-dnsop-internal
.lan would be much better name.
Re: Google .dev domain early access
#436Re: Google .dev domain early access
#437Earlier quoted context omitted.
ACME is an open protocol (and very soon it will be an IETF Internet Standard too). There are many alternative implementations. Just find one you trust. We actually did our own DNS-based implementation for our infrastructure.
I don't want to run someone else's code on my server just for this (the default certbot wants root access too, yikes), nor do I want to analyze someone else's implementation before running their code, and I sure as heck don't have the time, patience, or interest to write my own implementation of ACME just for the one service that uses it. I want to go to a website, have it tell me to put a string into a meta tag or D…
We do something similar, although not through a REST API. We handle all this cert management centralized on one server, which publishes the DNS records for DNS verification etc.
On our other servers is then just a simple script that periodically checks if the certs on the machine are near the expiry date and if so pulls a new one from the central system.
Re: Google .dev domain early access
#438I've had .dev domains for years. (Internally with Apache, virtual hosts IIRC?) It seemed like the obvious choice of suffix for my localhost experiments, and I can't be the only person using it (e.g. https://headsigned.com/posts/setting-up-local-development-do... ), will this new TLD break that? I suppose I can always edit my hosts file but if I didn't know a new TLD was dropping would it screw me silently?
[RFC2606] https://tools.ietf.org/html/rfc2606
Re: Google .dev domain early access
#439> A domain just for developers > $11,500 for 9 days early access Makes video games early access look like childs play.
> Can I buy a .dev domain even if I'm not a developer?
> Yes! From tools to platforms, programming languages to blogs, .dev is a home for all the interesting things that you build.