The search domain that every ISP is shoving in our throats is just another form of tracking/data mining and it's a very successful one,not far from what they use their DNS for.
Therefore if user chose the option Ignore WAN DNS the search domain automatically has to be removed and ignored as well.
So far by just removing and ignoring the WAN/ISP DNS is a half ass done job when it comes to...some form of privacy protection....IN MY OPINION
Hi,
I saw the above discussion from a thread for a recent build and wanted to discuss if there is any solution to fix this. For reference, I'm running an R8000 on build 47381 from 9/8/21.
So it looks like the search cinci.rr.com server has been forced into my search domain despite me having Ignore WAN DNS set, and also having no-resolv in my DNSMasq options. Is there something I might be missing?
Screenshots of your "Setup -> Basic Setup" and "Services -> Services" pages would help. You may want to read the help files associated with both pages ^_^
Screenshots of your "Setup -> Basic Setup" and "Services -> Services" pages would help. You may want to read the help files associated with both pages ^_^
Hi, I am attaching the requested screenshots of my config for you (I resized them to make them 50% smaller. Hopefully they are correct size). Please let me know if any other screenshots would be helpful - and thanks in advance!
Please note - the entire "additional Dnsmasq options" on is listed in the original post of this thread as you cannot see it in full on the screenshot.
Luckily you have no-resolv but your settings are not realy "optimal"
Local DNS should be kept at its default 0.0.0.0 when you use it as a normal gateway
Static DNS 1,2.3 should point to a DNS server higher up not to itself just leave it at 0.0.0.0
Luckily no-resolv overrides these wrong settings
It also has nothing to do with the original problem but other users might pick up the wrong idea from this.
Thank you very much for the feedback! I believe I got those settings from some very old websites when I first started using DD-WRT over 10 years ago, so those are clearly not optimal with all the advancements over the years.
I will change my Local DNS and static DNS to 0.0.0.0 as you suggested. Thanks again!
Joined: 16 Nov 2015 Posts: 6437 Location: UK, London, just across the river..
Posted: Tue Sep 14, 2021 11:05 Post subject:
using all-servers and query in a strict order along with no-resolv its not a good idea...
one of the best ways to avoid forced DNS by the ISP, is to use encrypted DNS...depends from your router you can use DNScrypt or SmartDNS via CLI, Unbound or Stubby check those green and red links in my signature...or sickies around forum regarding the others...
I recommend Stubby or SmartDNS as the easiest options... _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55630 WAP
TP-Link WR1043NDv2 -DD-WRT 55723 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55779 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55819 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55779 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
But some folks are *absolutely* certain that it's not a configuration issue that is the root cause of the upstream ISP search domain being shoved down their router's throat. ^_^ _________________ An old man said, “Erasers are made for those who make mistakes.” A youth replied, “Erasers are made for those who are willing to correct their mistakes!” Attitude matters! ~ Anonymous
----------
“You are always a student, never a master. You have to keep moving forward.” ~ Conrad Hall
----------
“Life is about moving on, accepting changes and looking forward to what makes you stronger and more complete.” ~ Anonymous
Joined: 08 May 2018 Posts: 14221 Location: Texas, USA
Posted: Tue Sep 14, 2021 16:28 Post subject:
The main issue is that "ignore wan dns" does not take into consideration "wan domain" information; this is what I discovered looking at the source code and passed over to @egc. There were already workarounds, but people didn't seem to want to look deep enough into it and create a solution until this was patched and fixed permanently. Thanks for your continued development support, @egc! _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net