![using namebench using namebench](https://images.sftcdn.net/images/t_app-cover-l,f_auto/p/cd7a8402-96d0-11e6-a650-00163ed833e7/954567405/namebench-screenshot.jpg)
TP-Link WR1043NDv2 -DD-WRT 47720 AP,NAT,AP Isolation,Ad-Block,Firewall,Local DNS,Forced DNS,DoT,VPN,VLAN Your solution is either use FFx DoH option on browser level or use Unbound-full DoT, Stubby DoT or DNScrypt on
![using namebench using namebench](https://2.bp.blogspot.com/_fxRR_bT3LgA/SyLXcptXT_I/AAAAAAAACDI/1-oIkQY3SGg/w1200-h630-p-k-no-nu/namebench.png)
![using namebench using namebench](http://3.bp.blogspot.com/_cNuMZYzxcps/S0Ukz6mUncI/AAAAAAAAApA/ippDw4OGHos/s400/html-result3-namebench.png)
This will eliminate the chance of your ISP DNS to sneak in.and will tell DNSmasq to use only those specified in server=īut than again, if your ISP is capping the traffic on port 53 and forcing it to their DNS resolver.U r done. If you use DNSmasq and local DNS you add those lines Location: UK, London, just across the river. Thanks again for your feedback, appreciate hearing other peoples experience/ideas I'll probably also later experiment with or try some of these dns-crypt solutions / DNS over HTTPS and similar things I've seen people write about. I hear google dns doesn't respect privacy too much, but then on the other hand, I think it's better for me than my current ISP. But ultradns is 77% slower, dynguide 100% slower, and opendns 160% slower. I think the conclusion is that google dns is on average -26% slower in response than my isp's dns. For a (or some) minute(s) those messages really made me think someone was really spying on me, but now it sounds like it's just normal namebench-output twitter / is hijacked: 172.217.21.132, warning messages and "how odd" (even though it sounds like it should say "how normal" instead) etc. So I guess then, that the namebench-output I see isn't unusual, it just scared me a bit about all this "hijacking", i.e. For example, if namebench tells you that Google, Facebook, and Paypal are hijacked, it probably just means that these companies have added IP addresses to their domain that namebench isn’t up to speed on. But in my experience, most of these are false positives. These notes can sometimes flag potential hacking, censorship or hijacking attempts. If you drill down deeper into the results, you’ll get some notes on the actual domain name resolutions. But after I read your answer I digged a bit more and found an excellent explanation here: - quote: Just a small comment first: "namebench" is supposedly a DNS benchmark-script and I'm also not very familiar with it. 8.8.8.8 and 8.8.4.4 as DNS servers instead of the default (from my ISP). Oh, thanks a lot, great suggestion about just setting the DNS and I imagined it would be a good idea to repeat the test, with e.g. There are too many errors/warnings, I think. Question: Is my ISP blocking public DNS-servers or? I don't understand it. Here's a link to the namebench-output (full output): All nameservers have warning: is hijacked: (likely a false positive) All nameservers have warning: is hijacked. (likely a false positive) All nameservers have warning: No answer (NXDOMAIN): static.ak. * Internal 192-1-1 failed test #2/7: Too many warnings (7), probably broken. * DynGuide failed test #2/5: Too many warnings (7), probably broken. Trying again with 6 threads (slow)",ĥ05 of 4514 servers are available (duration: 0:32:47.630533)ĭynGuide-2 failed test #1/5: static.ak.: No answer (NXDOMAIN): static.ak. "How odd! Only 11.2 percent of name servers were pingable. I don't understand the output from namebench.py - especially errors/warning about servers being "hijacked", too many warning, things appear broken (see the list below + attached). I tried the namebench.py script because I wanted to use another DNS-server than my ISP's (default) dns-servers. I want to setup my main router to use DNS-servers that don't belong to my ISP. The gateway at 192.168.1.1 also acts as a DNS-server with the following upstream DNS: I think it's because 192.168.1.1 is also the default gateway. I have the following hypothesis: I have 2 routers, 1 gateway, the other WAP. Posted: Tue 21:32 Post subject: namebench.py - Is my ISP blocking public DNS-servers?