DNS suffix bug, after update to version 1.6.0 Edit Location

[SonikV]

Describe the bug
DNS suffix parameter is ignored.
Even if the value is manually added to the database and displayed correctly in the web interface under Location settings,
it is not applied to VPN clients.
Clients only receive DNS server IP addresses, but not the search domain.

To Reproduce
Go to VPN → Locations → Edit location.
Add DNS servers and manually insert DNS suffix (ad.blabla.ua) into the database.
Confirm that the suffix appears in the web UI.
Connect a VPN client and check DNS settings.
Observe that the DNS suffix is not present on the client.

Expected behavior
The DNS suffix configured in the Location settings should be pushed to VPN clients along with DNS servers,
so that short names resolve correctly (e.g., host → host.ad.blabla.ua).

Version information

• Defguard Core version: v1.6.0
• Defguard Gateway version: v1.6.0
  • Operating system running the gateway: Debian 12

After updating to version 1.6.0, everything worked correctly — the DNS suffix was passed to clients. However, after making changes to the location parameters, it was not possible to save the settings until the domain ad.blabla.ua was removed from the DNS field. Once the domain was removed, the parameters could be saved. Even after manually adding the ad.blabla.ua parameter back into the database, nothing changed — the parameter is ignored.

[gstorme]

Hey, they fixed this today with release 1.6.1

[SonikV]

The problem remained after the update