<story><title>An extensive tutorial on how to setup a Pi-Hole</title><url>https://www.crosstalksolutions.com/the-worlds-greatest-pi-hole-and-unbound-tutorial-2023/</url></story><parent_chain><item><author>zrail</author><text>I treat my work laptop as a hostile entity on my network. It connects to a dedicated Wi-Fi network with client isolation enabled and on a dedicated VLAN with no access to other VLANs, just egress to the internet. DHCP serves 8.8.8.8 as DNS.&lt;p&gt;On the trusted VLAN I use Technitium as DNS and DHCP. I don&amp;#x27;t use any block lists, though, because I had too many complains from other network users. Technitium is mostly just because it&amp;#x27;s easy to manage DHCP hostnames and other DNS records in the same UI.</text></item><item><author>kingsloi</author><text>I used a Pi-Hole for all devices in my house, including my work MacBook. They manage their MacBooks with JamF, so most things are pretty locked down (including DNS settings in System Preferences). Sudo access is only possible if you open up the Self Service app, login, and issue yourself sudo&amp;#x2F;admin access for 6 hours. Once it expires, you have to issue yourself admin&amp;#x2F;sudo access again. No sudo = no changing DNS.&lt;p&gt;I set it and forgot it, until I went to Estes Park, Colorado over the Christmas holidays one year. I travelled with my MacBook just in case anything popped off... and it did. I logged into my MacBook, but quickly realised although I could connect to WiFi as normal, no DNS would resolve (it was pointed to 192.168.1.100 of my home network), and I couldn&amp;#x27;t connect to anything - including logging in the Self Service app to re-issue sudo access, to change the DNS. I had to walk a new colleague how to handle the scandal over the phone, driving through the mountains... thank goodness for good cell service!</text></item></parent_chain><comment><author>runjake</author><text>As a person who manages workplace malwar&lt;i&gt;^W&lt;/i&gt;device management software, this is a wise choice. You can gather &lt;i&gt;so much&lt;/i&gt; information from home networks, just by passively listening.</text></comment>
<story><title>An extensive tutorial on how to setup a Pi-Hole</title><url>https://www.crosstalksolutions.com/the-worlds-greatest-pi-hole-and-unbound-tutorial-2023/</url></story><parent_chain><item><author>zrail</author><text>I treat my work laptop as a hostile entity on my network. It connects to a dedicated Wi-Fi network with client isolation enabled and on a dedicated VLAN with no access to other VLANs, just egress to the internet. DHCP serves 8.8.8.8 as DNS.&lt;p&gt;On the trusted VLAN I use Technitium as DNS and DHCP. I don&amp;#x27;t use any block lists, though, because I had too many complains from other network users. Technitium is mostly just because it&amp;#x27;s easy to manage DHCP hostnames and other DNS records in the same UI.</text></item><item><author>kingsloi</author><text>I used a Pi-Hole for all devices in my house, including my work MacBook. They manage their MacBooks with JamF, so most things are pretty locked down (including DNS settings in System Preferences). Sudo access is only possible if you open up the Self Service app, login, and issue yourself sudo&amp;#x2F;admin access for 6 hours. Once it expires, you have to issue yourself admin&amp;#x2F;sudo access again. No sudo = no changing DNS.&lt;p&gt;I set it and forgot it, until I went to Estes Park, Colorado over the Christmas holidays one year. I travelled with my MacBook just in case anything popped off... and it did. I logged into my MacBook, but quickly realised although I could connect to WiFi as normal, no DNS would resolve (it was pointed to 192.168.1.100 of my home network), and I couldn&amp;#x27;t connect to anything - including logging in the Self Service app to re-issue sudo access, to change the DNS. I had to walk a new colleague how to handle the scandal over the phone, driving through the mountains... thank goodness for good cell service!</text></item></parent_chain><comment><author>tristor</author><text>Treating it as a hostile entity is definitely the right way to go.</text></comment>