I'm setting 1.1.1.1 Resolver in dhcp & Dns - Forward also I'm checked ignore resolve file but still all the Queries goes through My ISP dns resolver which Google Dns.
Also changing dns in Wan or Lan doesn't worked.
I tried to configure stubby too but then i lost internet access than.
Please guide me to configure 1.1.1.1 Resolver.
My building management own a server and they are providing internet to All apartment with captive portal maybe they have set in there system google DNS.
Please connect to your OpenWrt device using ssh and copy the output of the following commands and post it here using the "Preformatted text </> " button:
Remember to redact passwords, MAC addresses and any public IP addresses you may have:
ubus call system board
cat /etc/config/network
cat /etc/config/dhcp
cat /etc/config/firewall
As said on another thread, you need to get to the state where the redirect should happen.
There is no indication of a portal redirect in the result you posted.
Well, the portal uses just an IP address, not FQDN, so DNS is not required to access the portal.
I suppose you should first check if stubby or 1.1.1.1 will work alone (after the portal login) and then try to configure forwarding in dnsmasq.
root@androidtv:~# logread | grep nameserver
Sun Feb 23 00:26:36 2025 daemon.info dnsmasq[1]: using nameserver 10.0.0.1#53
Sun Feb 23 00:26:36 2025 daemon.info dnsmasq[1]: using nameserver 8.8.8.8#53
Sun Feb 23 00:26:36 2025 daemon.info dnsmasq[1]: using nameserver 8.8.4.4#53
Sun Feb 23 00:26:38 2025 daemon.info dnsmasq[1]: using nameserver 10.0.0.1#53
Sun Feb 23 00:26:38 2025 daemon.info dnsmasq[1]: using nameserver 8.8.8.8#53
Sun Feb 23 00:26:38 2025 daemon.info dnsmasq[1]: using nameserver 8.8.4.4#53
Sun Feb 23 13:30:58 2025 daemon.info dnsmasq[1]: using nameserver 1.1.1.1#53
Sun Feb 23 13:30:58 2025 daemon.info dnsmasq[1]: using nameserver 1.0.0.1#53
Sun Feb 23 13:30:58 2025 daemon.info dnsmasq[1]: using nameserver 1.1.1.1#53
Sun Feb 23 13:30:58 2025 daemon.info dnsmasq[1]: using nameserver 1.0.0.1#53
Sun Feb 23 13:30:58 2025 daemon.info dnsmasq[1]: using nameserver 10.0.0.1#53
Sun Feb 23 13:30:58 2025 daemon.info dnsmasq[1]: using nameserver 8.8.8.8#53
Sun Feb 23 13:30:58 2025 daemon.info dnsmasq[1]: using nameserver 8.8.4.4#53
Sun Feb 23 13:32:19 2025 daemon.info dnsmasq[1]: using nameserver 1.1.1.1#53
Sun Feb 23 13:32:19 2025 daemon.info dnsmasq[1]: using nameserver 1.0.0.1#53
Sun Feb 23 13:32:19 2025 daemon.info dnsmasq[1]: using nameserver 127.0.0.1#5453
Sun Feb 23 13:32:19 2025 daemon.info dnsmasq[1]: using nameserver 1.1.1.1#53
Sun Feb 23 13:32:19 2025 daemon.info dnsmasq[1]: using nameserver 1.0.0.1#53
Sun Feb 23 13:32:19 2025 daemon.info dnsmasq[1]: using nameserver 127.0.0.1#5453
Sun Feb 23 13:32:19 2025 daemon.info dnsmasq[1]: using nameserver 10.0.0.1#53
Sun Feb 23 13:32:19 2025 daemon.info dnsmasq[1]: using nameserver 8.8.8.8#53
Sun Feb 23 13:32:19 2025 daemon.info dnsmasq[1]: using nameserver 8.8.4.4#53
root@androidtv:~#
This is the only entry that should be there, you need to figure out where all the other addresses came from.
Typically we just need to use option peerdns 0 on wan but we also need to make sure that ntp domain or server is still resolvable using insecure DNS. You can use the same approach as in Secure DNS problem - #41 by AndrewZ