resolver

Alternately, a 3rd party dns operator can use anycast to control which resolver a given user uses, ensuring that the resolver is close to the user on the internet.

Running an internal DNS resolver is actually very cheap, almost every broadband CPE device runs or can run its own DNS proxy resolver.

DNS resolution time is important, but even if the google resolver returned results faster than your local ISP resolver it would still make your browsing in the general case slower.

If you use your local ISP as your resolver then you'll get an answer that's close to you.

If you use the google resolver you'll get an answer that's close to the google resolver and that will generate additional latency for all the rest of the browsing session.

As for your second point: The first time that `resolver` is called, arguments is in fact empty.

End result: you're farther away from the resolver, farther away from your web pages, farther away from your CDN.

All anyone needs to get to go/ is to put corp.google.com in their resolver search paths.

There was Resolver One, which apparently got acquired by PythonAnywhere, which allowed Python scripted spreadsheets.

Doesn't the author's setting of the resolver directive work for you, or is there something I'm missing?

I would have thought it would be evaluated when 'resolver' in invoked, and would therefore evaluate to an empty array.

BTW, I'm somewhere in systemd changelog with a security bugfix to an issue in systemd resolver.

Multistrap uses apt to do package selection and not the "stupid" dependency resolver that debootstrap uses.

Authoring react-resolver meant jumping through weird hoops to avoid context changing, but this release should mean things will work as expected, rather than having to sort out "gotchas".

There's been a push to standardize "Promise" to be the read-only side and "Future" to mean the resolver/promise pair, but Folly Futures use the opposite convention.

If you use Google's DNS service, because Google has your client IP, they can serve your content the fastest from the closest POP, however by using this DNS service you are actually creating an issue called "resolver proximity" for every CDN on the planet.