[dns-operations] Capturing 126.96.36.199 Traffic
geier at geier.ne.tz
Tue Feb 26 07:50:11 UTC 2013
your customer choose to use a DNS resolver very far away.
Though it's not nice and we don't like it, they are only hurting themselves.
First choice should still be education.
I don't know if Google can/wants/does give a different answer from the
resolvers for their own content, based on the query source.
But sure Akamai and friends can in the auth servers only see a google
resolver from a far away continent resolving for you :-) and so they
"think" you're there and a lot of content is fetched from far away...
Maybe your case should be on top of Google's Public DNS team for expansion
to new places...
because it causes a lot of "bad geo-location" based on big
On 2/25/2013 8:26 PM, Graham Beneke wrote:
> I discovered the other day that a large customer of $dayjob has decided
> that it is a good idea to outsource the LAN support for their head
> office and NOC to a mom-and-pop IT shop. While I question the wisdom in
> that, I was far more concerned by the fact that this mom-and-pop shop
> had configured Google Public DNS as the resolver for everything on their
> Now on my corner of the planet Google DNS is 190ms away. Never mind the
> mess we have with all the CDNs mapping their traffic to a different
> So what are you thoughts on capturing these queries and answering them
> on local resolvers that are <10ms away?
> The folks at Google are certainly not going to encourage us to spoof
> responses from their servers but are there any other potential pitfalls
> with doing this to save the customers from themselves?
More information about the dns-operations