How to utilize custom DNS for Kubernetes cluster

[r-pylypiuk-geniusee]

I’m trying to use a custom cluster DNS suffix with the NetBird operator:

cluster:
  dns: staging-cluster.local
  name: kubernetes-staging

I expose a Service following the docs and add:

annotations:
    netbird.io/expose: "true"
    netbird.io/policy: default
    netbird.io/resource-name: staging-api
    netbird.io/groups: staging

netbird shows the following for netbird network ls

Available Networks:

  - ID: argocd-staging
    Domains: main-api.api.svc.staging-cluster.local
    Status: Selected
    Resolved IPs: -

With this custom DNS suffix the name never resolves; using the default format it works fine.

Questions:
Is this expected, or am I missing a step to make custom cluster DNS suffixes resolvable via the operator?
Can I map a fully custom per-service hostname (e.g., api.vpn) via NetBird + the operator, so it points to my Service?