3 ms·
I can't help but wonder if they registered `.dev` because they have it internally routed on their corporate network now, and they don't want to all of a sudden
by bsimpson 12y ago
I can't help but wonder if they registered `.dev` because they have it internally routed on their corporate network now, and they don't want to all of a sudden have to deal with an employee not being able to read an article on a new blog help.dev because they also have a product called Help being tested at the internal URL help.dev.
If that's the case, them registering `.dev` might help everybody. It will give you a TLD that you can use for internal projects, knowing it will never conflict with a real site. Considering Apple's asinine handling of .local domains on iOS, a known-good alternative TLD could be a good thing.
- geofft 12y agoYeah, that was my first thought -- if Google registers .dev and keeps it in-house, this is good for the open web everywhere because we can all use it internally. Probably they can't say that to ICANN's face, but that sounds like it could have been a plausible intention all along. In fact, if Google registers .dev and promises to keep it in-house, they can then tell the Chrome team that it's okay to trust self-signed certs for .dev, or something, thereby letting us all use HTTPS for development.
- Kalium 12y agoThat... actually sounds hugely valuable for software houses everywhere.
- emmelaich 12y agoYou won't be able to use it internally unless you get split DNS and mangle your dns lookup configuration. Everything .dev resolves to 127.0.53.53 now. That ip address is a shot across the bow to warn you of the impending TLD registration. $ host blahflurgle.dev blahflurgle.dev has address 127.0.53.53 blahflurgle.dev mail is handled by 10 your-dns-needs-immediate-attention.dev.
- geofft 12y agoYou're going to have to set up split-DNS anyway if you want the records to resolve, right? Otherwise they would all NXDOMAIN.