I was able to set custom WAN DNS just fine on 1.4f firmware, however, on 1.4g it forces itself to use Google or Cisco DNS.
uci get network.wan.dns - Show’s correct DNS as entered, for me, NextDNS.
however, all my devices still use Cisco or Google.
After some investigating, the https dns proxy service is overriding my set DNS.
If i run /etc/init.d/https-dns-proxy stop - this fixes the issue until next reboot
I have spoken to three other R10 users on 1.4g - 2 out of 3 can replicate this issue.
Can confirm I can replicate this issue, typing in that command seems to fix it.
As per discord going to share this here for others:
Also in the script is the fix for your sticky WAN 
/cfg/post-cfg.sh
#!/bin/sh
echo "Running post-cfg.sh at $(date)" >> /tmp/debug.log
# Remove all https-dns-proxy instances
echo "Removing all https-dns-proxy instances..." >> /tmp/debug.log
while uci -q get https-dns-proxy.@https-dns-proxy[0]; do
uci delete https-dns-proxy.@https-dns-proxy[0]
done
uci commit https-dns-proxy
# Stop and disable the service
/etc/init.d/https-dns-proxy stop
/etc/init.d/https-dns-proxy disable
echo "https-dns-proxy disabled and wiped" >> /tmp/debug.log
# Set mwan3 sticky to 0
echo "Setting mwan3 sticky to 0..." >> /tmp/debug.log
uci set mwan3.default_pbr.sticky=0
uci commit
/etc/init.d/mwan3 restart
echo "post-cfg.sh finished at $(date)" >> /tmp/debug.log
also make sure the /cfg/post-cfg.sh is executable (chmod +x /cfg/post-cfg.sh)
Not sure if deleting the dns proxy is going to cause any issues but Alta guys can confirm
Cheers lobster legs, i owe you one! Cheers again for finding the dns root cause, script works perfectly
I TOLD YOU MY BURNT LEGS ARE FINE NOW thank you very much
Nice fix.
I bet Mr midget man is buzzing now haha.
Nice! Going to tuck this away to do some testing for later.
Also, didn’t realize there’s an Alta discord floating around out there either…
I’m sorry to be that guy but how on EARTH was this missed in testing. This firmware took a long time to release.
This was a DM as I know @LosSantosPro and @Sickyman_678
Hope the commands help
I’m not entirely sure tbh, bit unfortunate
Oh, fair enough lol
Thanks!
I think it’s a fair question!
Thinking back on it, I think I actually noticed this behavior while I was running the release candidate that was being offered although I brushed it off at the time due to other priorities and the fact it wasn’t causing any problems per se.
But I suppose that underscores the potential usefulness of community beta program or early adopter ring to help catch behavior like this before broad deployment.
Whats the discord link?
It was just a DM between me and @LosSantosPro
I can confirm that I too am experiencing the same issue with my custom DNS, for me, Control D. Will try the workaround later. Thanks all!
Can we not mark this as solved? It’s not solved–it’s a workaround for a serious regression, and the fix is a file that might cause other problems later when it’s actually fixed.
I was hitting my head against the wall why I was getting block page from Cisco (from my ISP) and just ignored it and tried another browser to avoid any weird plugin problems (Firefox, which is equipped to do DNS over HTTPS; only now do I realize why it accidentally sidestepped the issue).
Confirmed stopping the proxy fixes it temporarily.
Tbh I’ve given up, this Router has far too many problems, most recent ive discovered intermittent disconnection of LAN devices were caused by it, i was initially blaming my APs, it has been removed from my network, at least until someone is able to port OpenWRT / Luci to it
I can’t even sell it, as the buyer will almost definitely return it immediately or file a chargeback
I sold my UCG Fibre thinking i was getting a more stable setup, how wrong was I…
Okay, well, you’re entitled to bail on this, but again as the OP I’d not mark this as solved.
I love my Alta equipment, and have had a generally excellent experience. Regressions happen, but the speed at which a DNS leak isn’t being fixed is concerning, given that I’ve seen things fixed much faster in the past. I wouldn’t touch anyhing from UniFi ever again, even if you paid me.
It seems an admin has already removed the marked solution 