dns-server-setup
dnsleaktest
Our great sponsors
dns-server-setup | dnsleaktest | |
---|---|---|
5 | 5 | |
54 | 328 | |
- | - | |
2.7 | 0.0 | |
over 1 year ago | 2 months ago | |
Shell | Shell | |
GNU General Public License v3.0 only | MIT License |
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.
dns-server-setup
- Waktu Pendaftaran PSE sampai 27 Juli, Kominfo: Kalau Tidak Respons, Akses Diputus Sementara
-
There is a way to create a dns that use oisd?
Yes, looks like the code you're looking for lives in https://github.com/AhaDNS/dns-server-setup/blob/master/files/scripts/bash/unbound_update.sh
-
Adguard not working properly
Haha I know what you mean :) On the bright side it is open-source: https://github.com/AhaDNS/dns-server-setup
dnsleaktest
-
Should i use my vpn provider's native client or use a wireguard/openvpn client instead?
I am currently trying out Guetun in docker with ExpressVPN but am getting possible DNS leaks reported by this test. I ran this test in the docker exec console for my qBittorrent container which is routed through my Gluetun container. This is the output I get after running. I have also tried some other tests like doileak.com torrent IPtest. The reults i get from that say that I have an ipv4 udp leak. How do i know for sure that I'm not leaking my IP? TIA!
-
Do I need to install Stubby or dnscrypt-proxy ?
If you want to check what DNS is being used system-wide. https://github.com/macvk/dnsleaktest
-
Please, help me understand how my IP was leaked
I've confirmed the following: * curl ifconfig.cc inside the qbittorrent container gives me the VPN IP, not my own. * Using https://ipleak.net shows my VPN IP, not my own, when downloading their torrent in qbittorrent. * When using https://github.com/macvk/dnsleaktest inside my qbittorrent container, I get a different set of DNS server than when using it outside of it. These are the servers specifically from inside: You use 6 DNS servers: 104.156.251.15 [United States of America AS20473 The Constant Company LLC] 107.191.42.180 [United States of America AS20473 The Constant Company LLC] 144.202.14.9 [United States of America AS20473 The Constant Company LLC] 2001:19f0:5:18e8:5400:1ff:febe:3032 [United States of America AS20473 The Constant Company LLC] 2001:19f0:300:60d2::33 [United States of America AS20473 The Constant Company LLC] 2001:19f0:300:6256:5400:ff:fe1a:c6e7 [United States of America AS20473 The Constant Company LLC]
-
DNS for wireguard interface inside netns (with systemd-resolved)
I recreated the simple (wg moved into netns) setup and introduced the nsswitch file you posted above. I then ran a DNS leak test script from within the netns and it didn't report any leaks. I ran wireshark in parallel, and unlike before, there was no DNS traffic on the host's ethernet interface. This looks really promising.
What are some alternatives?
Technitium DNS Server - Technitium DNS Server
Pi-hole - A black hole for Internet advertisements
ansible-adguard - Ansible playbook to setup AdGuard Home with Unbound, including DoH, DoT & Let's Encrypt, based on Docker
sdns - A high-performance, recursive DNS resolver server with DNSSEC support, focused on preserving privacy.
doh-cf-workers - DNS-over-HTTPS proxy on Cloudflare Workers
arch-privoxyvpn - Docker build script for Arch Linux base with Privoxy and OpenVPN
namespaced-openvpn - Wrapper for OpenVPN on Linux solving various privacy issues
systemd - The systemd System and Service Manager
vpn-only-network-namespace
unbound-docker - Unbound DNS Server Docker Image
dcompass - A high-performance programmable DNS component aiming at robustness, speed, and flexibility
Mosdns-on-PaaS - Deploy DNS over HTTPS service on PaaS platforms (Heroku, Okteto, etc.) | 在 Heroku / Okteto 等免费 PaaS 服务平台上部署 Mosdns