Management omits persisted nameserver groups from peer network maps

Summary

In a self-hosted deployment, Management 0.77.1 persists an enabled conditional nameserver group and its peer-group assignments, but sends affected Windows peers a network map with an empty DNSConfig.

Environment

• Management: netbirdio/management 0.77.1
• Client: Windows 0.77.1
• Self-hosted Management and Dashboard

Configuration

• One enabled nameserver group with one resolver at port 53
• One match domain
• Distribution groups include the built-in All group and a custom group
• The test peer is confirmed in both distribution groups in the Management SQLite datastore

Expected behavior

The test peer receives the configured nameserver group in its network map and resolves the configured match domain through that resolver.

Actual behavior

After restarting the NetBird service, the peer receives a fresh network map but the DNS section is empty:

"DNSConfig": {
  "ServiceEnable": false,
  "NameServerGroups": [],
  "CustomZones": []
}

The client reports dnsServers as an empty array. Its tunnel adapter has no DNS server and no NRPT rule. The configured match domain resolves through the local DNS provider and returns NXDOMAIN. A packet capture on the configured resolver receives no query from the peer.

Persistence verification

The Management SQLite datastore confirms the nameserver group is enabled, has the expected resolver and match domain, and references the expected distribution-group IDs. The group_peers table confirms the test peer is a member of the built-in All group and the custom distribution group.

Additional notes

• Recreating only the Management container after updating 0.77.0 to 0.77.1 did not change the result.
• Dashboard displays the nameserver group, its match domain, and its distribution groups correctly.
• A sanitized debug bundle is available for maintainers through a private channel; it is not attached publicly because it contains internal metadata.

Request

Could maintainers identify why Management omits a persisted nameserver group from the generated peer network map, and advise any required server-side configuration or migration?