[Bug]: Webtop not resolving DNS with custom DNSDomain
Open
@knikhilm is already working on this.
Since Aug 7, 2026.
bug
- Dominant language
- HTML
- Stars
- 30
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
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
- Deploy a 9.1 instance with the
-DNSDomainflag set - Wait for full deployment
- 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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.