<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /></head><body style='font-size: 10pt'>
<p>On 21/11/2017 10:39, Damian Menscher wrote:</p>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0"><!-- html ignored --><!-- head ignored --><!-- meta ignored -->
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote"><br class="gmail_quote" />
<blockquote class="gmail_quote" style="margin: 0 0 0 .8ex; border-left: 1px #ccc solid; padding-left: 1ex;">
<div style="font-size: 10pt;">
<div>
<div class="h5">
<blockquote style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0;">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div> </div>
<div>Actually the users *do* care, which is why they explicitly changed their settings from the ISP default to 8.8.8.8.</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
<div> </div>
<div>Maybe I'm old school, but I dont see a need for any open public resolvers, those that run them, dont do it out the kindness of their heart, there is always a commercial reason.</div>
</div>
</blockquote>
<div> </div>
<div>You're right, there is a commercial reason Google operates an open public resolver: "our business depends on functional internet, so let's provide users an alternative to slow, broken, or actively malicious ISP servers."</div>
<div> </div>
<div>I suppose you'll have us believe the ISPs are hijacking 8.8.8.8 to their own systems out of the goodness of their hearts, and not for some commercial reason (which is likely exactly what the users are trying to avoid)? Sorry, but I don't buy the claim that hijacking another company's address space to violate the express intent of your users is something you're doing just to be nice.</div>
<div> </div>
<div>Damian</div>
</div>
</div>
</div>
</blockquote>
<p><br /></p>
<p>I think we all know googles reasons far exceed the "functional internet" reasoning.</p>
<p>The reason we stopped allowing third party DNS was way back because clients would often use other DNS severs, mostly previous ISP's DNS's when churning services over, and would nearly always result in support getting "slow sites" , "takes ages to respond" complaints, the support guys quickly realised what was going on, once changing to ours all complaints about slow sites ended, its also why we anycasted our own cache DNS's in each states PoP since our own users on other side of country found delays too that also vanished.</p>
<p>It was extended to include distributed lists of malware, phishing and virus laden sites to return NXDOMAIN, in recent years RPZ was also used for dangerous domains, and court ordered blocked sites, since we could send them to a landing page.</p>
<div>So yes, there are non commercial reasons for doing that stuff.</div>
<div> </div>
<div>-- <br />
<p>Kind Regards,</p>
<p>Noel Butler</p>
<table border="1" width="748" cellspacing="0" cellpadding="5">
<tbody>
<tr>
<td style="text-align: left;"><span style="font-size: 10pt;"><small><small><small><small>This Email, including any attachments, may contain legally privileged information, therefore remains confidential and subject to copyright protected under international law. You may not disseminate, discuss, or reveal, any part, to anyone, without the authors express written authority to do so. If you are not the intended recipient, please notify the sender then delete all copies of this message including attachments, immediately. Confidentiality, copyright, and legal privilege are not waived or lost by reason of the mistaken delivery of this message. Only <a href="http://www.adobe.com/">PDF</a> and <a href="http://en.wikipedia.org/wiki/OpenDocument">ODF</a> documents accepted, please do not send proprietary formatted documents </small></small></small></small></span></td>
</tr>
</tbody>
</table>
</div>
</body></html>