The WAN port of Flint2 is connected to LAN port of my ISP Modem/Router.
Flint2 is getting the DNS from my ISP Modem/Router.
Is there an way the computers connected to Flint2 to use the DNS set on it instead of using the DNS distribuited by my ISP Modem/Router?
On my ISP Modem/Router I can set just “Manual DNS (like 1.1.1.1, 8.8.8.8) or Automatic DNS (my ISP DNS)”, but there is no encrypted DNS available on it like on Flint2.
If I go to the client connected to Flint2 and type “ipconfig /all” (cmd Windows prompt), I can see the DNS is that one from my ISP Modem/Router and not that specified on Flint2
and if that does not work ipconfig /renew since dns is given by dhcp?
though its strange if override settings for all clients does not work, I would think its a forward which hijacks all dns traffic right?
in that case can you try this: nslookup -type=TXT whoami.ds.akahelp.net
I had once a different issue with overriding dns and it made me think it really did not work on dnsleaktest even with flushing, or chrome://net-internals/#dns but the command here above is a really good test in my situation it show it did worked
the ips it first spits out should be your new dns… maybe external so you can whois them to verify
You Encrypted DNS/DoH looks proper. Engaged DNS Rebinding & fire up IP Leak using Incognito/Private Mode after flushing per @xize11 , @admon 's respective notes.
Related: I find it always best to use Incognito mode when administrating a GL or OpenWrt device; browser caching can be a b!7ch in causing ‘false positive’ errors & weird inconsistencies. YMMV.
Also just a hint , if you use DoT or DoH or even a vpn on the client device itself not the router, then there is a chance you skip your settings and overriding does not work then.
Overriding requires normal dns port 53, DoH and DoT uses 853,443, the vpn skips a hop entirely, so unless the dns is set in the vpn config with allowance to lan, otherwise theres a chance it will not work.
Jup that is idd strange but maybe a caching / flush issue.
Or… OP uses some type of exotic configuration (i.e different device than br-lan, or guest) and the scripts may not work with this, but then i think it should be reflected in luci. , there was a time some of these scripts did add interoperability to uci/luci firewall directly but not all of them.
But in this image you have more then just NextDNS - that’s why Cloudflare will answer.
If you want to use NextDNS, you should remove all others - or change the order (if its possible)
The 2nd image in the 1st post shows that you are trying to use cloudflare as main server for DNS-over-HTTPS. The picture from DNS Detect says that you are using cloudflare. Soooo… that’s what you configured.