dnsproxy-config
dnsproxy
Our great sponsors
dnsproxy-config | dnsproxy | |
---|---|---|
12 | 56 | |
12 | 2,169 | |
- | 2.5% | |
0.0 | 8.3 | |
over 1 year ago | 8 days ago | |
Shell | Go | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
dnsproxy-config
-
Pihole DNS over TLS/HTTPS
Yes.
-
Is DNS over HTTPS Supported?
You can find the project here, the documentation describes installation alongside or in front of Pi-hole, depending on the use case. If you want secure incoming traffic, a certified FQDN is required. This is left as an exercise for the user (to raise the bar somewhat).
-
Cloudflared installation on Pi Zero W
No need for the full AGH stack. You can easily run dnsproxy alongside or in front of Pi-hole.
-
Has anyone actually 100% confirmed that a device on their network (TV/PC/Mobile (including specific apps) have actually bypassed their pihole by using hard coded DoH (DNS over HTTPS)? If so, which device/app?
I have somewhat documented the process of putting up a Do(H|T|Q)/DNScrypt proxy as a standalone service here.
-
Internet accessible Personal DNSoverHTTPS Server?
I still need to fix up a couple of permission issues in my documentation, but I have the rough outline of deploying dnsproxy as a standalone simple service here. The last few edits I made to it were getting it to use the yaml syntaxed config file, and trying to make sure a default configuration should Just Work without having to edit it, but you'd still want to.
-
(Android) Private DNS via PiHole
There's a basic overview here, but I haven't touched it for a while and the documentation may be slightly broken surrounding exec permissions on some files.
-
Chrome/Edge is not using my Pihole DNS but using DNS-over-HTTPS
It's very possible. You could easily set this up yourself. I do so so myself using dnsproxy, and you could too.
-
What's the best way to make a Pi-Hole highly available?
I have an example dnsproxy service here that I use for high availability (one-to-many) distribution and providing encrypted transport.
-
Munin Monitoring: munin-pihole-plugins
You might know me as that Unbound guy, or maybe even that dnsproxy guy. Today I would like to make myself known as that Munin guy, and introduce munin-pihole-plugins for Munin Monitoring.
-
Check on Android which app is spamming the PiHole
Kinda.
dnsproxy
- AdGuard Simple DNS Proxy with DoH, DoT, DoQ and DNSCrypt Support
-
Adguard adblocker vs Adguard DNS?
There's no difference between the free and freemium in regards to customizability while using VPN since both offer DoT endpoints. On Android, with the standard WireGuard & OpenVPN app you can use any DoT provider you want since the Android Private DNS setting takes precedence over the DNS settings in the VPN app. In Windows you can run https://github.com/AdguardTeam/dnsproxy locally, that way the VPN won't intercept and modify the local DNS traffic (the DNS upstream still goes through the VPN, but if you use DoT/DoH/DoQ then it continues to the DNS server you prefer).
-
VPN recommendation with DoH or DoQ
Which OS is this? In Android the Private DNS (DoT) setting is respected by some clients like the standard WireGuard & OpenVPN, so you can just load any provider's config and enter your personal DoT address. In iOS Passepartout can accept WG/OpenVPN config and apply custom DoH, as for desktop OS you can just run https://github.com/AdguardTeam/dnsproxy forwarding to your DoH/DoQ address and set the VPN interface to use localhost as DNS.
-
Privacy threat: needing to choose between VPN and DNS
If it's on a desktop/laptop, you can run https://github.com/AdguardTeam/dnsproxy to forward into your NextDNS DoH/DoT/DoQ, and set your VPN network adapter to use 127.0.0.1, 127.0.0.2, ::1 and ::2 for DNS (the secondary entry either loopback or fail entirely, all it matters is your OS shouldn't try other address), that way since local traffic isn't routed by the VPN, you still get NextDNS (the actual DoH/DoT/DoQ traffic is still going through the VPN).
-
Adguard on windows blocking dns rewrite of adguard home
Why not set AdGuard Home (assuming it's indeed installed at your home) to use DoT/DoH/DoQ upstream (so your ISP can't redirect it) and have the rewrites in AGH too? If your AGH instance isn't at home, assuming you're using Windows 11 set your AGH to listen on DoH and set Windows to use DoH to your AGH. Otherwise use dnsproxy in Windows to forward it to your AGH through DoT/DoH/DoQ.
- ISP di Indonesia sudah bisa deteksi penggunaan DNS over HTTPS/TLS?
-
Adguard Home and DNS-over-HTTPS
I'm not sure what is your plan here, do you need the Surfshark feature specifically, or do you just want to hide your traffic from your ISP? If you need Surfshark (perhaps for streaming geoblocked content or torrenting), then integrating it with AGH hosted on the cloud for device-wide traffic is going to be complicated. The Surfshark client doesn't support custom DoH/DoT address nor IPv6 (opening public IPv4 Do53 is a big no-no, you'll get swamped for DNS amplification attack), so you'll need an app running on your device to redirect DNS traffic like https://github.com/AdguardTeam/dnsproxy to your cloud AGH. You'd need to setup DoH with a custom path through Nginx otherwise people would scan your server and use it, plus if Google's crawler sees the AGH login page it will mark it as deceptive, and your entire domain is blacklisted by the Safe Browsing API that's used on multiple products (Chrome, Firefox, AdGuard, NextDNS, etc). With all that hassle might as well just run AGH locally on your device anyway (local traffic isn't handled by VPNs)
-
Client Settings Cached?
Assuming you have a custom upstream, it's by design
-
Feature Requests: Force use QUIC or DoQ Protocol, AnyCast/Ultralow toggle settings
Since nextdns-cli isn't likely to support DoQ anytime soon, your best bet is dnsproxy and ctrld.
- Feature Request: Different DoH per network i.e. different NextDNS per network.
What are some alternatives?
homelab-pihole
Unbound - Unbound is a validating, recursive, and caching DNS resolver.
uptime-kuma - A fancy self-hosted monitoring tool
mosdns - 一个 DNS 转发器
gravity-sync - 💫 The easy way to synchronize the DNS configuration of two Pi-hole 5.x instances.
doh-cf-workers - DNS-over-HTTPS proxy on Cloudflare Workers
unbound-config - fragmented configuration files for unbound recursive dns resolver
jp.tiar.app - jp.tiar.app
lighttpd-external-munin-proxy - lighttpd external.conf for Munin webserver proxy
nextdns - NextDNS CLI client (DoH Proxy)
munin-pihole-plugins - A set of Munin plugins for monitoring various Pi-hole® stats
wirehole - WireHole is a combination of WireGuard, Pi-hole, and Unbound in a docker-compose project with the intent of enabling users to quickly and easily create a personally managed full or split-tunnel WireGuard VPN with ad blocking capabilities thanks to Pi-hole, and DNS caching, additional privacy options, and upstream providers via Unbound.