No, they mean setting your DNS to an already existing ad blocking DNS. You do not need a oi hole to do that. See option 2 here https://adguard-dns.io/en/public-dns.html
I do this on my router and phone. It doesn’t block everything, sure, but it blocks more than you’d think. And I didn’t have to fiddle with a raspberry Pi.
Company’s are catching on to this and hard coding their apps to google dns. This is why it only works sometimes and the best option is to setup either pihole or adguard home dns and use firewall rules to forward all dns to it.
Block DNS outbound. The only DNS you get is what I give you. Oh, you can’t resolve an address because you’ve hardcoded your app? Well, I guess I don’t get to watch that ad, which is the same result as if you used my DNS.
Maybe i made it sound weird. Use a firewall to catch all dns traffic trying to leave the network and route it the PiHole/Adguard Home. This is how to make sure nothing, not even hardcoded dns on any app on any device, wont be filtered. I personally block google dns IPs on top of this but that’s just a precaution.
Ohh, yeah, I think that might work. I don’t really know the ins and outs of low level DNS stuff. With HTTPS that wouldn’t work unless you had some sort of self signed cert on your device, but I don’t think normal regular DNS traffic is encrypted at all. I see a lot of folks talk about the privacy aspect of it, so, yeah, maybe you can do that more easily.
Is this something Pi Hole can do by itself? (With some settings on your router as well, of course, because you already have to set it as the DNS.)
You would need a firewall to provide any type of blocking or port forwarding. Most routers provide some basic ability to do this but it’s hit or miss and depends on the manufacturer. I came from a modded merlin asuswrt Asus router firmware to an opnsense firewall running on custom hardware.
That’s literally what a pi-hole is.
No, they mean setting your DNS to an already existing ad blocking DNS. You do not need a oi hole to do that. See option 2 here https://adguard-dns.io/en/public-dns.html
I do this on my router and phone. It doesn’t block everything, sure, but it blocks more than you’d think. And I didn’t have to fiddle with a raspberry Pi.
Company’s are catching on to this and hard coding their apps to google dns. This is why it only works sometimes and the best option is to setup either pihole or adguard home dns and use firewall rules to forward all dns to it.
Block DNS outbound. The only DNS you get is what I give you. Oh, you can’t resolve an address because you’ve hardcoded your app? Well, I guess I don’t get to watch that ad, which is the same result as if you used my DNS.
Firewall would help, yeah, but I don’t think PiHole would with a hard coded DNS server.
Maybe i made it sound weird. Use a firewall to catch all dns traffic trying to leave the network and route it the PiHole/Adguard Home. This is how to make sure nothing, not even hardcoded dns on any app on any device, wont be filtered. I personally block google dns IPs on top of this but that’s just a precaution.
Ohh, yeah, I think that might work. I don’t really know the ins and outs of low level DNS stuff. With HTTPS that wouldn’t work unless you had some sort of self signed cert on your device, but I don’t think normal regular DNS traffic is encrypted at all. I see a lot of folks talk about the privacy aspect of it, so, yeah, maybe you can do that more easily.
Is this something Pi Hole can do by itself? (With some settings on your router as well, of course, because you already have to set it as the DNS.)
You would need a firewall to provide any type of blocking or port forwarding. Most routers provide some basic ability to do this but it’s hit or miss and depends on the manufacturer. I came from a modded merlin asuswrt Asus router firmware to an opnsense firewall running on custom hardware.