[dns-operations] Capturing 126.96.36.199 Traffic
Carlos M. Martinez
carlosm3011 at gmail.com
Mon Feb 25 17:46:53 UTC 2013
On principle I would hate my ISP messing around with my traffic,
regardless of any good intentions.
On 2/25/13 3: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