I was using Wireguard up to the last update (4.6.2). Before that, I could add a search domain to the DNS configuration on Wireguard, iike:
DNS=192.168.20.0, mydomain.local
Now the router doesn't allow me to enter a search domain on the DNS setting, which is a common Wireguard configuration.
Is there a way to achieve this?
Best,
Francis
192.168.20.0 is a network address, not an IP.
Change this value to the IP of your DNS server/forwarder.
This was not the real value, it was just an example. LEt's say
DNS=8.8.8.8, mydomain.local
is not working.
I am having the same issue. Hope there is a resolution soon. For now my workaround is to manually update this on each client.
Just a nitpick - this would depend on the subnet mask, technically.192.168.20.0 would be a valid IP address if the subnet is 21 bits or larger.
Edited: had to correct, 22 should still use 20.0 as network - 21 or larger would be correct. My bad.
True, but many software will just break then ... 
Yes, my ISP assigned me a .0 address once, it caused some issues with some sites. Short-sighted filtering methods - but I was the one who paid the price for their crap filtering. I just changed my MAC and got a new address once I got tired of messing with it.
I think the point got lost here.
Can confirm this issue in version 4.7.0/4.0.
Wireguard spec says that DNS = 8.8.8.8, mydomain.local should be a valid configuration to specify search domain but the item and file configuration form both fail validation for it.
Force inserting the domain search value by manually editing /etc/config/wireguard or by manually editing a validated form submission accepts the values but doesn't actually change the behavior. It seems the implementation doesn't respect the domain search parameter at all. I haven't tried abandoning the GL-iNet Wireguard GUI and using the LuCI plugin yet but will probably do so and report back here if it's a valid workaround while GL-iNet works on meeting spec.
Possible workaround here