wgroeneveld
/
brainbaking
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

addendum dns stuff

This commit is contained in:
Wouter Groeneveld 2022-02-23 21:21:02 +01:00
parent f1fc889071
commit 934c3f5a66
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
content/post/2022/02/how-to-setup-pi-hole-on-synology-nas.md
View File

@ -44,3 +44,10 @@ Yet another problem. Once the Pi-Hole is done with your DNS request, it has to p
![](../pirunning.jpg "The Pi-hole up and running on Xavier, our (internal networked) NAS.")
_Pfew_. In the end, my limited networking skills might have led me to over-engineer the first solution, but I'm glad it works flawlessly now. The only challenge that remains---besides fiddling with blacklisting domains---is: what if the NAS goes down? For the moment, I don't feel like buying a Raspberry Pi just to install a backup DNS server, but it's certainly possible. Time will tell how stable the NAS OS itself is.
---
**Addendum**: After reading through [this excellent guide on how to choose the DNS server](https://blog.frehi.be/2019/03/07/which-dns-server-to-use/) and checking if my ISP supports DNSSEC (it does) and QNAME minimisation (it doesn't), I decided to test Cloudflare's `1.1.1.1` public provider. It does have a server in Brussels, and the nearest Quad9 is in Amsterdam. For even more privacy, I could also setup [DNS-over-HTTPS](https://docs.pi-hole.net/guides/dns/cloudflared/).
Someday.