The DNS configured in WireGuard is not being applied to the client.

[Armanjafari]

Although the DNS field is set in the WireGuard core, it is not exported in the QR code configuration and must be added manually after importing the profile.

[JavadMoqaddam]

WireGuard subscription URIs (wireguard://...) generated by the panel exclude the dns parameter.

Root Cause:
This issue is caused by the following line in app/subscription/base.py, which explicitly removes the DNS key from the URI payload:
line 222: uri_payload.pop("dns", None)

Impact:
While clients like V2Ray import the configuration successfully without the dns parameter, the official WireGuard client (and other standard WireGuard implementations) relies on this parameter to apply the tunnel's DNS settings. Stripping it from the URI prevents these clients from configuring the DNS correctly, resulting in a DNS leak, as the device falls back to the system/ISP DNS instead of using the tunnel's resolver.