<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>DNS on</title><link>http://salopst.yearl.us/tags/dns/</link><description>Recent content in DNS on</description><generator>Hugo</generator><language>en</language><copyright>&lt;a href="https://creativecommons.org/licenses/by-nc/4.0/" target="_blank" rel="noopener"&gt;CC BY-NC 4.0&lt;/a&gt;</copyright><lastBuildDate>Sat, 16 Jun 2018 07:18:05 +0000</lastBuildDate><atom:link href="http://salopst.yearl.us/tags/dns/index.xml" rel="self" type="application/rss+xml"/><item><title>Pi-hole DNS-level ad blocker</title><link>http://salopst.yearl.us/pi-hole-dns-level-ad-blocker/</link><pubDate>Sat, 16 Jun 2018 07:18:05 +0000</pubDate><guid>http://salopst.yearl.us/pi-hole-dns-level-ad-blocker/</guid><description>&lt;p&gt;Getting pretty annoyed with keeping track of which browser on which machine has which add blockers installed, so it&amp;rsquo;s time for a more holistic approach. Enter, stage left, the &lt;a href="https://pi-hole.net/"&gt;Pi-hole&lt;/a&gt;. In short it:&lt;/p&gt;&#10;&lt;blockquote&gt;&#10;&lt;p&gt;&amp;hellip;acts as a forwarding DNS server, which means if it doesn’t know where a domain is, it has to forward your query to another server that does. When you install Pi-hole, it knows where the ad-serving domains are (because you tell it), so it doesn’t forward those requests.&lt;/p&gt;&#10;&lt;/blockquote&gt;</description></item></channel></rss>