4 ms·

>http://go/codegolf http://go/codegolf How does this work, some sort of TLD magic? (That shouldn't be possible, right?) Is it just routed within Google's inter

by rory096 11y ago

>http://go/codegolf http://go/codegolf How does this work, some sort of TLD magic? (That shouldn't be possible, right?) Is it just routed within Google's internal network?

dmayle 11y ago
By default foo resolves to foo.mydomain.mytld (man resolv.conf, section domain), so as long as the machines are configured with a local domain, this will work.
cornstalks 11y ago
It works the same as any other corporate network: either custom DNS resolution on the machine (i.e. /etc/hosts), DNS resolution in the internal network, or DNS resolution on the VPN. Or, more likely, a mix of the 3. To get to go links, you've got to be connected to Google's network (either physically, or through VPN). It's essentially the same as accessing a computer on your LAN with its host name (in which case, the router can do the DNS lookup and resolution for the internal network).
- thrownaway2424 11y ago
  Fascinating but totally incorrect analysis. All anyone needs to get to go/ is to put corp.google.com in their resolver search paths. Of course, such people will also need a google.com login to actually be redirected to the destination.
tperson 11y ago
I'd assume the same way localhost works on your computer.
deleted 11y ago
[deleted]
ot 11y ago
It's probably resolved by the internal network DNS. You can do the same even with your home router.
jsmthrowaway 11y ago
Search paths. The full address is go.corp.google.com (which is simply a URL shortener), IIRC; however, I think the resolvers are also configured to respond to a bare name in a lot of cases as an optimization. They talk a little bit about corp in their BeyondCorp paper[0], which is well worth a read, and I'm speaking to ancient memory so I might be wrong these days. [0]: http://static.googleusercontent.com/media/research.google.com/en//pubs/archive/43231.pdf http://static.googleusercontent.com/media/research.google.co...
- deleted 11y ago
  [deleted]
- rory096 11y ago
  Thanks for the link! Figured it was a bit more complex than just a host file, being Google and all.
asuffield 11y ago
When you're on a corp device, your DNS search path includes google.com. It's not magic at all, it's over here: http://goto.google.com/ http://goto.google.com/ (You're going to see a login page that you can't authenticate to)
darkhorn 11y ago
It redirects to http://go.com/ http://go.com/
- darkhorn 11y ago
  Okay, I've got it. Redirects because of my DNS.

by rory096 11y ago

>http://go/codegolf http://go/codegolf How does this work, some sort of TLD magic? (That shouldn't be possible, right?) Is it just routed within Google's internal network?

dmayle 11y ago

By default foo resolves to foo.mydomain.mytld (man resolv.conf, section domain), so as long as the machines are configured with a local domain, this will work.

cornstalks 11y ago

It works the same as any other corporate network: either custom DNS resolution on the machine (i.e. /etc/hosts), DNS resolution in the internal network, or DNS resolution on the VPN. Or, more likely, a mix of the 3. To get to go links, you've got to be connected to Google's network (either physically, or through VPN). It's essentially the same as accessing a computer on your LAN with its host name (in which case, the router can do the DNS lookup and resolution for the internal network).

thrownaway2424 11y ago
Fascinating but totally incorrect analysis. All anyone needs to get to go/ is to put corp.google.com in their resolver search paths. Of course, such people will also need a google.com login to actually be redirected to the destination.

tperson 11y ago

I'd assume the same way localhost works on your computer.

deleted 11y ago

[deleted]

ot 11y ago

It's probably resolved by the internal network DNS. You can do the same even with your home router.

jsmthrowaway 11y ago

Search paths. The full address is go.corp.google.com (which is simply a URL shortener), IIRC; however, I think the resolvers are also configured to respond to a bare name in a lot of cases as an optimization. They talk a little bit about corp in their BeyondCorp paper[0], which is well worth a read, and I'm speaking to ancient memory so I might be wrong these days. [0]: http://static.googleusercontent.com/media/research.google.com/en//pubs/archive/43231.pdf http://static.googleusercontent.com/media/research.google.co...

deleted 11y ago
[deleted]
rory096 11y ago
Thanks for the link! Figured it was a bit more complex than just a host file, being Google and all.

asuffield 11y ago

When you're on a corp device, your DNS search path includes google.com. It's not magic at all, it's over here: http://goto.google.com/ http://goto.google.com/ (You're going to see a login page that you can't authenticate to)

darkhorn 11y ago

It redirects to http://go.com/ http://go.com/

darkhorn 11y ago
Okay, I've got it. Redirects because of my DNS.