![[IMG]](../../../assets/img/network-switch.B.jpg)
Pi-hole ad-blocking DNS server
Wanting to use a Windows 10 VM for running Studio Tax, but really not wanting to have Windows automatically update on me, I decided to see how well the Pi-hole ad-blocking DNS server would work.
As the name implies, Pi-hole is designed to run on a Raspberry Pi. However, for testing purposes I decided instead to run it in a Proxmox VM. Because the Pi’s operating system (Raspian) is descended from Debian, I initially chose Debian 8 for this. But it didn’t really work properly, so I instead used a small CentOS 7 VM. That worked much better.
I set up the VM on IP address 192.168.1.112, and configured Windows to use that
as its preferred DNS server. The only real problem I had was getting Windows to
talk to Samba on penguin: it could map a network drive, but cmd.exe didn’t
recognize Z: as a valid drive. But that’s not all that important, because the
program that need to talk to the Z: drive (Studio Tax) can do that with no
problems.
Additional blacklist entries
-
data.microsoft.com(wildcard) -
mp.microsoft.com(wildcard) -
update.microsoft.com(wildcard)