There are quite a few Russian lastnames that end ”dev”, like Medvedev. I think there is going to be quite a rush for these.
Google .dev domain early access
131–140 of 475 posts
Re: Google .dev domain early access
#132Google is such a big company, I find it bizarre they are trying to make money in this way. It would be interesting to know what they make at the end of the pre-sale.
Re: Google .dev domain early access
#133I hope they fail. Google forced me to migrate my local .dev domains to .devo because Chrome refused to connect to my localy configured domain names via /etc/hosts.
Isn't this just as silly as wishing Cloudflare's public DNS fails because you were using 1.1.1.1 as a development IP ?
- The IP address 1.1.1.1 as a public DNS has clear value to the public, DNS IP addresses needing to be for 0-255 values that are memorable. .dev has no real public value considering the plethora of other tlds.
Re: Google .dev domain early access
#134> You can purchase an SSL certificate through one of our web partners or a Certificate Authority. Read this article to learn more. Really? No mention of Lets Encrypt? Does anyone still buy certificates nowadays, especially for dev sites?
Let's Encrypt provides DV (Domain Validation). Not OV (Organization Validation).
Obviously .dev is intended for software development and most domains there would probably be using DV only so this might not apply to it, though.
Re: Google .dev domain early access
#135I hate the new trend of companies having multiple domains with different TLDs, as I never know this way if it's the same company or not.
Re: Google .dev domain early access
#136I'll never forgive them for competing with my hosts file. .test is not as nice
Re: Google .dev domain early access
#137Damn, now I have to change my hosts file, I've been using .dev for local development
https://security.stackexchange.com/questions/14802/if-someon...
But generally speaking a subdomain on a domain you really own seems like a better idea.
https://serverfault.com/questions/17255/top-level-domain-dom...
Re: Google .dev domain early access
#138Does anyone know how the “premium” renewal prices are set and governed? I’m going through this right now with .app domains (also owned by Google). Apparently domains categorized as “premium” have a much higher yearly pricing, and how it’s priced is not specified anywhere on the registry website. I called a few registrars and they said that the premium pricing is set by the registry. What’s concerning is that the regi…
"Registry Operator must have uniform pricing for renewals of domain name registrations (“Renewal Pricing”). For the purposes of determining Renewal Pricing, the price for each domain registration renewal must be identical to the price of all other domain name registration renewals in place at the time of such renewal, and such price must take into account universal application of any refunds, rebates, discounts, product tying or other programs in place at the time of renewal."
REGISTRY AGREEMENT - 2.10 (b)
https://newgtlds.icann.org/sites/default/files/agreements/ag...
Re: Google .dev domain early access
#139Having used "sudo vi /etc/hosts" to add .dev domains, this gets no I'm going to avoid buying one, but if there are any popular .dev domains I hope I will forget about it before long. I don't want negative feelings from this so often. On the other hand there are plenty of reminders of negative things in politics and the environment, so I guess I've gotten used to it and developed outrage fatigue.
https://tools.ietf.org/html/rfc2606
.test is only one more letter.
Re: Google .dev domain early access
#140Earlier quoted context omitted.
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.
According to RFC 2602 [1], > 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. So it might work but it could be problematic if the intent is to use ".localhost" as a local network domain rather than just the loc…