Setting option 6 is a good idea, you can also change DNS=64.6.64.6 to DNS=10.0.0.1 for example in wg.conf.
Confirmed it's an issue.
Hi again, I'm back to report that this issue has returned.
The fix worked great in version 4.7.4 and in all the beta builds of 4.8.0, but the problem came back in the last RC of 4.8.0, and it’s still present in the stable 4.8.0 release.
The only way I was able to resolve it was by using the workaround that @Vampire_Duchess suggested:
However, I want to add that my setup is slightly different from @Vampire_Duchess’s:
- I don’t use Pi-hole as the DHCP server, only as the DNS resolver.
- I can access all local services normally, even when connected through the VPN.
- The problem is that DNS requests are sent through the VPN’s DNS servers, not Pi-hole — even when the “Allow Custom DNS to Override VPN DNS” toggle is enabled in the GL.iNet interface.
I also tried resetting the router completely on 4.8.0 to see if that would help, but the issue remained.
However, when I downgraded back to the stable build 4.7.4, everything worked correctly without needing to change anything in LuCI.
3 Likes
Update: I’m experiencing the same problem with the built-in WireGuard server when using VPN Cascading. When my iPhone connects as a client, DNS traffic goes through the VPN instead of the Pi-hole, even though the client is set to use Pi-hole’s IP for DNS. This only happens when the VPN client (the outgoing VPN) is enabled. When the VPN client is off, the iPhone connects and DNS works correctly via Pi-hole. For now, I will downgrade back to version 4.7.4 where everything works as expected.
1 Like
thank you for this I was noticing the same, keep a safe copy of the 4.7.4 we were almost there. Hopefully they can check what is going on.
1 Like
Yeah, this has taught me a lesson to always save old builds somewhere, especially the betas. I really wish there was an archive page. I will miss the new features until this gets fixed
2 Likes
I tested the Mango V2 again with stable firmware version 4.3.25, and the issue still persists, DNS resolution doesn't work when connected via VPN. Unfortunately, the problem is confirmed, and the only available solution is still to apply the workaround. I don't believe this behavior has changed.
I also tested the GL-AR750S-EXT (Slate) with the 4.7.2 Beta firmware, and DNS resolution works correctly there. However, the stable firmware for the Slate is currently the same as the Mango (4.3.25), and the issue is present in that version as well. I doubt we’ll see a fix in something like 4.3.26, and it’s unlikely that the 4.7.2 Beta will be made available for the AR750S-EXT or for Mango either.
At this point, it’s unclear whether a fix will be included in a future firmware update, possibly between 4.7.2 and 4.7.4 (currently stable for Beryl). Unless that happens, applying the workaround (fixing the DNS command) remains the only viable option. 
I checked on the Beryl the DNS resolution is working on the beta 7 of 4.8.0 I don't have the file and I notice the stable is 4.8.0 release 3. so there must be something there.
3 Likes
Update
I just tried to flash the nightly build of 4.8.0 (2025-08-04) as the release notice mentioned some fixes related to DNS that came after the latest stable release, and I can report I’m still experiencing the same problem there too. I saw that @bruce liked my first update post, so I am guessing the team is looking into it?
2 Likes
The 4.8.0 version is completely broken – you should not install it under any circumstances.
Hi,
Yes, R&D is planning to check
1 Like
Update, can not reproduce this issue
Do you know if is possible to have a link for the beta 7 of the firmware 4.8.0? Im currently traveling but I don't have with me the file anymore of the beta, so If use the final release 3 of 4.8.0 I'm afraid that I'll get the bug.
Hi, you can upgrade to v4.8.1 latest snapshot: