vmware / vmware/Holodeck

[Bug]: Webtop not resolving DNS with custom DNSDomain

Open
#164 2 comments 0 reactions 1 assignee View on GitHub

@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
  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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.