[dns-operations] Capturing 220.127.116.11 Traffic
sm at resistor.net
Mon Feb 25 18:06:46 UTC 2013
At 09:26 25-02-2013, Graham Beneke wrote:
>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
A lot of people use 18.104.22.168. I don't know whether it is due to the
lemming  effect or swarm intelligence.
>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?
DNS interception is not a good idea in my opinion.
>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?
Once that becomes popular the regulator might wish to "standardize"
it (see draft-iab-filtering-considerations-02). Saving the customers
from themselves is a good intention.
1. Lemmings are small rodents that have been known to follow each
other as they charge to their deaths off the edge of cliffs. This is
actually an unsubstantiated myth about lemmings.
More information about the dns-operations