Live data from Hacker News

Google .dev domain early access

domains.google

31–40 of 475 posts

Re: Google .dev domain early access

#31
post #12

The .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.

If you've any developers on your team that use MacOS, avoid .local since it does some listening on this for Bonjour: https://blog.scottlowe.org/2006/01/04/mac-os-x-and-local-dom...

I believe .localhost is the "official" recommended TLD for local development.

Re: Google .dev domain early access

#32

Earlier quoted context omitted.

If you've been using .dev for local development, that means you've either been setting it in your hosts or using your own DNS server until now, which you can continue to do with a .dev TLD.

Chrome requires an SSL certificate for all .dev hostnames.

if you have the technical savvy to be using .dev before the Google deployment, you have the technical savvy to install an additional root cert for use with Chrome.

Re: Google .dev domain early access

#33

I was already irritated that they took the .dev TLD. This sort of blatant money grab over it is simply gross. $8k premium to get in on the first day.

They didn’t take it. They applied, went through the process, and paid a premium for it.

$8k for a domain is actually cheap compared to other premiums in other new gtlds.

Re: Google .dev domain early access

#34
I'm not familiar with ICANN rules, but I wonder if a company can do whatever they want to a gTLD once it's accepted, even if it's not within the intended usage in the gTLD application? As far as I know, Google said they registered .dev for internal use and for Google-related products and it will be completely closed to Google, according to their application[1]:

> The mission of this gTLD, .dev, is to provide a dedicated domain space in which Google can enact second-level domains specific to its projects in development. Specifically, the new gTLD will provide Google with greater ability to create a custom portal for employees to manage products and services in development.

> Charleston Road Registry intends to operate the proposed gTLD as a closed registry with Google as the sole registrar and registrant. The goal of the proposed gTLD is to allow Google to manage the domain name space for its projects in development. The proposed gTLD will provide Google with the ability to customize its domain and website names for its projects and signal to users that .dev websites are managed by Google

> Charleston Road Registry believes that given its intended use by Google, the .dev gTLD will best add value to the gTLD space by remaining completely closed for the sole use of Google.

…and now they're opening it up to the public... :\

[1]: https://gtldresult.icann.org/applicationstatus/applicationde...

Re: Google .dev domain early access

#35

Besides the usual disregard decency let's HSTS preload a TLD people have been using for local development for decades... This is terrible gatekeeping and I hope Google perishes soon. Wow. I can't get over how fucking dumb this is. This is the mark of a corporation filled with people that thinks putting a price tag on supposedly scarce good early will deter bad actors. Clearly everyone who thought this up has way too…

Yes, this, though I really am disappointed in ICANN here. ICANN should not have sold a TLD known to be in heavy use already. Their desire for cash from this process seems to have overwhelmed their good sense in managing the domain system.

Yeah, well. That's got nothing to do with .dev. All the new TLDs are fucking dumb. Just a cash grab for the ICANN. Might as well get rid of TLDs altogether.

Re: Google .dev domain early access

#36

Earlier quoted context omitted.

If you've been using .dev for local development, that means you've either been setting it in your hosts or using your own DNS server until now, which you can continue to do with a .dev TLD.

Chrome requires an SSL certificate for all .dev hostnames.

Is there a good reason not to use HTTPs now if it’s a public facing site?

Re: Google .dev domain early access

#37
post #32

Earlier quoted context omitted.

Chrome requires an SSL certificate for all .dev hostnames.

if you have the technical savvy to be using .dev before the Google deployment, you have the technical savvy to install an additional root cert for use with Chrome.

What about internal use in organizations?

Sorry but this is pure malice by Google. I can invert this argument by saying if you're buying a .dev domain you have the technical savvy to get on an HSTS preload list, except you haven't broken anyone's workflow.

EDIT: And I mean... have you USED openssl's x509 toolchain? That's a few steps up from editing the hostsfile.

Re: Google .dev domain early access

#38
post #30

Earlier quoted context omitted.

Why do you need to use .test or .local? Presumably you were already editing your hosts file or running your own DNS server in order to make .dev resolve for local development, which you can continue to do?

HSTS is required for .dev

Install a root cert? Takes 1 minute.

Re: Google .dev domain early access

#39
post #18

A domain just for developers! Until it abruptly shuts down Feb 19, 2021. Why would anyone trust Google with something with any kind of long-term requirements as important as a name? They should have registered ".chump" instead, because that is really what users of a Google-managed TLD are declaring "Dear VALUED developer, thanks so much for being a part of the .dev experiment! After a long hard period of staring at o…

A TLD "with benefits" from Google is a money-printing press. While Google has a certain track record, this makes it rather unlikely for them to discontinue it in the near future.

Re: Google .dev domain early access

#40
post #12

The .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.

Why do you need to use .test or .local? Presumably you were already editing your hosts file or running your own DNS server in order to make .dev resolve for local development, which you can continue to do?

[deleted]
Post reply on HN