[Bug]: Webtop not resolving DNS with custom DNSDomain

[certanet]

Holorouter Version

9.1

VCF Version

VCF 9.1

Target Type

vCenter Cluster

Describe the bug

When providing a custom domain with the -DNSDomain flag to New-HoloDeckInstance, the deployment works fine, but the Holorouter Webtop interface doesn't resolve any of the FQDNs. Lookups from external sources work correctly, as does internal product-to-product lookups, just Webtop it seems doesn't.
Accessing by IP is fine, so connectivity is there, but vCenter specifically redirects to the FQDN (which fails).
Using curl in webtop also fails to resolve.

Reproduction steps

1. Deploy a 9.1 instance with the -DNSDomain flag set
2. Wait for full deployment
3. Try to access the FQDN of any of the deployed components

Expected behavior

The FQDN is resolved and connectivity to the product works.

Relevant logs

Additional context

No response

[knikhilm]

Can you please share the output of /holodeck-runtime/k8s/coredns_configmap.yaml and /holodeck-runtime/templates/coredns_configmap.yaml for further triage?

[certanet]

Unfortunately this deployment is in an air-gapped environment so I can't get the files.

However, I've just deployed a fresh Holorouter 9.1 and the contents of the file is the same in all four places, so you can view it by deploying the OVA:

VM	File	Same Contents
Fresh Holorouter 9.1	/holodeck-runtime/k8s/coredns_configmap.yaml	✅
Fresh Holorouter 9.1	/holodeck-runtime/templates/coredns_configmap.yaml	✅
Holorouter 9.1 that's deployed Holodeck instance hd01	/holodeck-runtime/k8s/coredns_configmap.yaml	✅
Holorouter 9.1 that's deployed Holodeck instance hd01	/holodeck-runtime/templates/coredns_configmap.yaml	✅

The custom DNSDomain is hd01.lab if that makes a difference.