Bottom-line - my dns leak tests keep showing my ISP DNS servers with Wireguard, although my IP address correctly shows my wireguard connection. PEr the luci interface, my Wireguard connection is up and running.
The rest of the story: I have the latest OpenWRT I just installed on a Cudy TR3000. Smooth install. I installed the luci and wireguard software, sans problems. Loaded my Wireguard profile, sans problem. The same wireguard profile I use on my gl-inet sft-1200, and all my other devices. The gl-inet is rock solid but because it's still has the 18+ series software, I figured an upgrade was due.
There must be a stupid simple setting I'm missing. And yes, I have named DNS servers in the "Advanced" tab of the Wireguard setup. I've tried various combinations of DHCP and DNS settings to no avail. I've set the "Firewall" tab in the Wireguard interface to my WAN interface. What am I missing?
Unfortunately using dns weight and strict order is not a very reliable solution, DNSMasq gives up really quick so there is a real chance of leakage nonetheless.
See my notes about this subject:
If the default routing is via WireGuard it just does not matter what DNS servers you are using as all traffic goes via WireGuard.
Problems usually arise if you are using Policy Based routing. So the question is are you?
At one point I reset OpenWRT to all the defaults, loaded my profile, and configured using the Wireguard protocol screens/tabs. I only set the DNS server (via my loaded profile) and the Firewall tab to "WAN". And I never set the strict order and dns weight settings. I've never had to do that in all my previous Wireguard settings.
It can help if you show us your configs, please connect to your OpenWRT device using ssh and copy the output of the following commands and post it here using the "Preformatted text
Remember to redact keys, passwords, MAC addresses and any public IP addresses you may have but do not redact private RFC 1918 IP addresses (192.168.X.X, 10.X.X.X and 172.16-32.X.X) as that is not needed:
ubus call system board
cat /etc/config/network
cat /etc/config/dhcp
cat /etc/config/firewall
ip route show
wg show
Not related to your actual problem but what do you want with IPv6?
Your WireGuard interface seems to be able to use IPv6.
Now on to your problem:
You have WireGuard as default route so everything including traffic from the router and from DNSMasq should use that default route:
You can pick any DNS server you want and that will use the WG default route except a DNS server directly upstream because you have a specific route via the wan directly upstream: