5 ms·
Google Search to redirect its country level TLDs to Google.com
- spiderfarmer 2y agoThis is so they can use the same tracking cookies across all their products.
- jsheard 2y agoGoogle owns the .google TLD, could they theoretically use https://google https://google or is that not allowed?
- redserk 2y agoNot sure if that’s allowed, but that sure feels like a throwback to AOL keywords if it was — just at the DNS level.
- deleted 2y ago[deleted]
- equinoxnemesis 2y agoNot allowed for gTLDs. Some ccTLDs do it, http://ai/ http://ai/ resolved as recently as a year ago though I can't get it to right now.
- jsheard 2y agoGoing by the Wayback Machine it looks like it used to redirect to http://www.ai http://www.ai, which still works, but only over HTTP.
- Thorrez 2y agoWell of course http://www.ai http://www.ai would work. That's no different from http://foo.ai http://foo.ai . http://uz./ http://uz./ serves a 500 error.
- sph 2y agoYou need a dot at the end for it to resolve correctly https://ai https://ai. It’s unreachable anyway
- weird-eye-issue 2y agoThat is cursed
- Natfan 2y agoYou're currently browsing `news.ycombinator.com.`[0]. [0]: https://jvns.ca/blog/2022/09/12/why-do-domain-names-end-with-a-dot-/ https://jvns.ca/blog/2022/09/12/why-do-domain-names-end-with...
- sph 2y agoIt is not, it is for your local resolver to distinguish a top-level domain from a subdomain (i.e. `foo` gets rewritten to `foo.mydomain.com` or `foo.local`) man resolv.conf, read up on search domains and the ndots option
- banana_giraffe 2y agohttps://xn--l1acc./ https://xn--l1acc./ and https://uz./ https://uz./ connect, though there's a cert issues in both cases.
- franze 2y agoSeems like a pretty big SPOF
- beardyw 2y agoI think they probably know what they are doing.
- snowwrestler 2y agoI wonder if this is related to the first party cookie security model. That is supposedly why Google switched maps from maps.google.com to www.google.com/maps. Running everything off a single subdomain of a single root domain should allow better pooling of data.
- abxyz 2y agoSubdomains were chosen historically because it was the sane way to run different infrastructure for each service. Nowadays, with the globally distributed frontends that Google's Cloud offers, path routing and subdomain routing are mostly equivalent. Subdomains are archaic, they are exposing the architecture (separate services) to users out of necessity. I don't think cookies were the motivation but it's probably a nice benefit. https://cloud.google.com/load-balancing/docs/url-map-concepts https://cloud.google.com/load-balancing/docs/url-map-concept...
- gardenhedge 2y agoSubdomains can be on the same architecture
- snowwrestler 2y agoYes it’s easy route paths, I’ve been using Fastly to do it for years. But the vast majority of users don’t care about URL structure. If a company goes through the effort to change them, it’s because the company expects to benefit somehow.
- ndriscoll 2y agoL4 vs L7 load balancing and the ability to send clients to specific addresses seem like major differences to me? I'm not seeing how subdomains are "archaic". It's also obviously desirable on the user side in a world of everything using TLS to allow better network management (e.g. blocking some services like youtube and ads on a child's device while allowing e.g. maps. Or if reddit used subdomains, you could allow e.g. minecraft.reddit.com without allowing everything else) without needing to install CAs on every device to MITM everything.
- phillipseamore 2y agoThis has been working the other way up until now right? At Google scale redirecting requests to ccTLD versions uses up plenty of resources and bandwidth: Get request to .com (like from urlbar searches) GeoIP lookup or cookie check Redirect to ccTLD Much of this is then repeated on the ccTLD. This change should decrease latency for users (no redirect, no extra DNS lookups, no extra TLS handshake) and enhance caching of resources.