Academy/Holodeck Lab Setup & Operations/External Access, DNS, and Routing Configuration
This lab targets VCF 9.0.2

External Access, DNS, and Routing Configuration

VCF 9.0.2Intermediateadminnetworkvcdx⏱ 60 min

Core workflow applies to VCF 9.0.0 through 9.0.2 with Holodeck 9.0.2. HoloRouter routing and DNS principles are version-agnostic and apply to VCF 5.2.x nested instances as well. Source-checked 1 Oct 2026 against the Holodeck 9.0.2 documentation at vmware.github.io/Holodeck/9.0.2/ (index: Holodeck Environment Overview, Holorouter Overview, Concepts, Pre-requisites, Deployment, Post Deployment, Day 2 Operations, How To; cmd_reference; FAQ) and, where VCF behaviour is described, the VCF 9.0.1 documentation. In Holodeck 9.x the toolkit is a PowerShell module built into the HoloRouter OVA (Photon OS): the operator SSHes to the HoloRouter, runs pwsh, and works under /holodeck-runtime. There is no Windows HoloConsole, no C:\Holodeck path, no -ConfigFile parameter and no separate Prepare phase. Rewritten for v8.2.2 after the 360-degree audit.

Objectives

  • Describe the HoloRouter network architecture: the external management interface, the Site A trunk interface carrying VLANs 0 and 10-25 on 10.1.0.0/20 (Site B: VLANs 40-58 on 10.2.0.0/20), and the services it provides (DNS forwarder, DHCP, NTP, L3 routing, firewall, BGP, proxy)
  • Reach the nested estate from the webtop (http://<holorouter-ip>:30000) and understand its 9.0.2 security caveat
  • Reach the nested estate from an external workstation by routing the Holodeck CIDRs via the HoloRouter external IP and pointing DNS at it
  • Manage DNS entries on the HoloRouter with Get-/Set-/Remove-HoloDeckDNSConfig and verify records with Get-HoloDeckAppNetwork
  • Handle certificate trust for the nested VCF consoles and the proxy path for outbound access
  • Design access patterns for several workstations and for VPN users, and the firewall exposure each one creates

Prerequisites

holodeck-02 complete with a healthy management domain; a workstation on the external network with administrative rights to change its routes and DNS; the HoloRouter external IP known.

Prior labs: holodeck-02

Required skills:

  • IP routing and DNS fundamentals
  • Workstation route and DNS configuration (Windows, macOS or Linux)
  • Browser certificate handling
📸 Starting State: S3-9x — Management Domain Deployed (VCF 9.x)

Lab Environment

HoloRouter with an External interface (management IP on the external network) and a Site A trunk interface carrying the Holodeck VLANs. The nested estate (10.1.0.0/20) is reachable only through the HoloRouter, which routes between the external network and the Holodeck subnets, answers DNS for vcf.lab as a forwarder, and proxies outbound access.

Mermaid source
graph LR
  WS[External workstation] -->|route 10.1.0.0/20 via HoloRouter ext IP; DNS = HoloRouter ext IP| HR[HoloRouter]
  WS -->|http://ext-ip:30000 webtop| HR
  HR -->|VLAN 10-25 trunk, L3 routing, firewall| MGMT[Nested mgmt subnet: vc-mgmt-a, sddcmanager-a, nsx-mgmt-a, ops-a, esx-01a..04a]
  HR -->|proxy| NET[Internet / depot]

IP Addressing

NetworkPurposeVLAN
10.1.0.0/20Default Holodeck Site A master CIDR, subdivided by New-HoloDeckNetworkConfig into the Site A subnets (management, vMotion, vSAN, host overlay, edge uplinks, and others)VLANs 0 and 10-25 (Site A default)
10.2.0.0/20Default Holodeck Site B master CIDR (dual-site only)VLANs 40-58 (Site B default)
<external management network>HoloRouter external management IP (DHCP or static, set at OVA deployment); the only external IP a Holodeck environment needsExternal port group

Credentials

SystemUsernamePassword
HoloRouter (SSH and pwsh)rootSet in the OVA Additional settings at deployment
HoloRouter webtop(no authentication in 9.0.2)http://<holorouter-ip>:30000; the docs warn not to expose it externally
Management vCenteradministrator@vsphere.localHolodeck documented default (Post Deployment table)
SDDC Manageradministrator@vsphere.localHolodeck documented default (Post Deployment table)
Management NSXadminHolodeck documented default (Post Deployment table)

Tasks

Task 1 Understand the HoloRouter network architecture and services

Manageability

Every access path goes through the HoloRouter. Knowing which interface, VLAN set and service does what is the whole of this lab.

Step 1

From the outer vSphere layer record the HoloRouter VM's network adapters: Management on the External port group (one IP, DHCP or static, set at OVA deployment), Site A and Site B on the trunk port group.

Adapter-to-port-group map and the external IP recorded.
Step 2

Write down the default VLAN and CIDR plan from the documentation: Site A uses VLANs 0 and 10 through 25 on 10.1.0.0/20; Site B uses VLANs 40 through 58 on 10.2.0.0/20; custom VLAN ranges need at least 16 consecutive IDs for Site A and 19 for Site B; the default DNS domain is vcf.lab (service FQDNs are <name>.site-a.vcf.lab).

VLAN/CIDR/DNS plan recorded.
Step 3

In pwsh on the HoloRouter (config imported) list the subnets and gateways: Get-HoloDeckSubnet -Site a | ft -AutoSize. Identify the management subnet and its gateway (the HoloRouter's interface in that VLAN).

Management subnet, VLAN ID and gateway identified.
Step 4

List the services the documentation gives the HoloRouter: DNS (local to each site, acts as forwarder), DHCP (local to each site), NTP, L3 routing between the sites' VLANs, firewall (traffic to and from external networks and between nested networks), BGP (peering with the NSX Tier-0 for overlay egress), proxy (controls outbound connectivity), job scheduling, webtop, PowerShell with PowerCLI.

Service list with the role each plays for external access (DNS, routing, firewall, proxy, webtop).
Step 5

Record the two documented access paths: UI access through the webtop at http://<holorouter-ip>:30000 from a jump host or console that reaches the external IP; CLI access with ssh root@<holorouter-ip>.

Both paths recorded.
Step 6

Note the Holodeck isolation statement: each environment is self-contained, needs a single external IP, and removes the need for VLAN and BGP connections in the customer network. List what that means for your firewall: only the HoloRouter external IP is exposed, on SSH (22) and webtop (30000) plus whatever you route.

Exposure summary: one IP, two services by default.
Step 7

Get-HoloDeckAppNetwork -Site a: capture the FQDN-to-IP map for every appliance you will reach (vc-mgmt-a, sddcmanager-a, nsx-mgmt-a, ops-a, vcfinstaller-a, esx-01a..04a).

Appliance map captured.
Step 8

Draw the access diagram: workstation, HoloRouter external IP, trunk VLANs, management subnet, appliances.

Diagram saved.

Validation Gate

Check: Adapters, VLAN/CIDR plan, subnets and gateway, services, two access paths, exposure summary, appliance map and diagram recorded.

Expected: You can explain every hop between a workstation and a nested console.

Common Errors

Assuming the nested subnets are reachable directly
Cause: They exist only behind the HoloRouter.
Fix: Route through the HoloRouter external IP (Task 2).
Thinking the HoloRouter runs VCF components
Cause: Architecture confusion.
Fix: It runs infrastructure services only; VCF components are nested VMs.
Expecting Site B addresses in a single-site lab
Cause: Site B exists only after a dual-site deployment.
Fix: Use Site A values unless holodeck-06 has been done.

Task 2 Route from an external workstation through the HoloRouter

Manageability

The webtop works but is slow and, in 9.0.2, unauthenticated. A routed workstation is the normal way to work; it needs one static route and DNS.

Step 1

On your workstation add a static route for the Holodeck Site A CIDR via the HoloRouter external IP. Windows (admin): route add 10.1.0.0 mask 255.255.240.0 <holorouter-ext-ip>. macOS: sudo route -n add -net 10.1.0.0/20 <holorouter-ext-ip>. Linux: sudo ip route add 10.1.0.0/20 via <holorouter-ext-ip>. Make it persistent if you will reuse it (Windows -p).

route add 10.1.0.0 mask 255.255.240.0 <holorouter-ext-ip> -p
Route present in the workstation routing table.
Step 2

Test reachability to the management gateway and to an appliance IP from Get-HoloDeckAppNetwork: ping <mgmt-gateway> and ping <vc-mgmt-a-ip>. If ICMP is filtered, test TCP 443 instead (for example with curl -k https://<ip>/ or a port test).

Nested management IPs reachable from the workstation.
Step 3

If the workstation is on a different subnet from the HoloRouter external IP, the static route must point at a next hop on your own subnet (your router), and that router needs the route to 10.1.0.0/20 via the HoloRouter external IP. Record which model applies.

Route placement decided: on the workstation (same subnet) or on the site router.
Step 4

Repeat for Site B (10.2.0.0/20) if holodeck-06 is or will be deployed; custom CIDRs replace the defaults.

Routes for every deployed site.
Step 5

Confirm return traffic: the HoloRouter must route back to your workstation's subnet via its external gateway; the external gateway/DNS set at OVA deployment (or by DHCP) provides this. If replies fail while forward packets arrive, check that external gateway.

Bidirectional traffic confirmed.
Step 6

Check the HoloRouter firewall role from the documentation (controls traffic to and from external networks and between nested networks): record which inbound flows work by default from your workstation (443 to appliances, 22 to nested hosts) and note anything blocked.

Observed inbound flow table.
Step 7

Open https://<vc-mgmt-a-ip>/ by IP to prove routing before DNS; expect a certificate warning (Task 4).

vSphere Client login page by IP.

Validation Gate

Check: Static route in place; nested IPs reachable; return path confirmed; flow table recorded; console reachable by IP.

Expected: Routed access without the webtop.

Common Errors

Route added but no reply
Cause: Return path missing on the HoloRouter's external gateway, or ICMP filtered.
Fix: Check the HoloRouter external gateway and test TCP 443 instead of ping.
Route works from one PC but not others
Cause: Route added per workstation.
Fix: Put the route on the site router (Task 5 patterns).
Workstation on a remote subnet cannot reach the HoloRouter IP as next hop
Cause: Next hop must be on-link.
Fix: Point the route at your local router and add the route there.
Only the external IP responds; nothing behind it
Cause: Firewall on the HoloRouter or a wrong CIDR in the route.
Fix: Verify the CIDR from Get-HoloDeckSubnet and the HoloRouter firewall behaviour.

Task 3 Resolve nested FQDNs from the workstation

Manageability

The HoloRouter is the DNS server for vcf.lab and a forwarder for everything else. Your workstation either uses it as DNS or your site DNS forwards the zone to it.

Step 1

Option A (single workstation): set the HoloRouter external IP as the workstation's DNS server (the documentation's model: the HoloRouter DNS acts as a forwarder for other names). Test: nslookup vc-mgmt-a.site-a.vcf.lab <holorouter-ext-ip>.

The appliance IP from Get-HoloDeckAppNetwork is returned.
Step 2

Option B (shared site): on your site DNS create a conditional forwarder for vcf.lab (and the custom -DNSDomain if used) to the HoloRouter external IP; keep workstation DNS unchanged. Test the same lookup through the site DNS.

Site DNS resolves vcf.lab names via the forwarder.
Step 3

Inspect the HoloRouter records in pwsh: Get-HoloDeckDNSConfig (all), Get-HoloDeckDNSConfig -FQDN sddcmanager-a.site-a.vcf.lab, Get-HoloDeckDNSConfig -IP <ip>.

Records for every appliance listed.
Step 4

Add a record for a jump host or lab VM you will deploy: Set-HoloDeckDNSConfig -DNSRecord '10.1.1.201 harbor.site-a.vcf.lab' (the record must be in single quotes). Verify with Get-HoloDeckDNSConfig -FQDN harbor.site-a.vcf.lab and from the workstation.

Set-HoloDeckDNSConfig -DNSRecord '10.1.1.201 harbor.site-a.vcf.lab'
New record resolves.
Step 5

Update it: Set-HoloDeckDNSConfig -SearchDNSRecord '10.1.1.201 harbor.site-a.vcf.lab' -ReplaceDNSRecord '10.1.1.210 harbor.site-a.vcf.lab' (no -Update switch: the Holodeck 9.0.1 release notes removed it and infer the update from the two parameters; the Getting Started page still shows the old syntax). Then remove it: Remove-HoloDeckDNSConfig -DNSRecord '10.1.1.210 harbor.site-a.vcf.lab'.

Record updated, then removed; Get-HoloDeckDNSConfig confirms each step.
Step 6

Test reverse resolution for an appliance IP from the workstation (nslookup <ip>), since VCF components require forward and reverse records.

PTR returned for the appliance IP.
Step 7

Open https://vc-mgmt-a.site-a.vcf.lab, https://sddcmanager-a.site-a.vcf.lab, https://nsx-mgmt-a.site-a.vcf.lab and https://ops-a.site-a.vcf.lab by name from the workstation.

All four consoles load by FQDN.
Step 8

Record the DNS design choice (workstation DNS vs conditional forwarder) and its consequences for other users and for internet resolution through the HoloRouter forwarder.

DNS decision documented.

Validation Gate

Check: Lookups via the HoloRouter and/or site forwarder; records listed, added, updated, removed with the cmdlets; reverse lookup works; consoles load by FQDN.

Expected: Name resolution for the nested estate from the workstation.

Common Errors

Names resolve on the HoloRouter but not on the workstation
Cause: Workstation DNS still points elsewhere and no forwarder exists.
Fix: Use Option A or B.
Set-HoloDeckDNSConfig rejects the record
Cause: Record not in single quotes or wrong 'IP FQDN' order.
Fix: Use -DNSRecord '<ip> <fqdn>' exactly as documented.
Internet names fail after switching workstation DNS to the HoloRouter
Cause: HoloRouter forwarder cannot reach upstream DNS.
Fix: Check the DNS/gateway given at OVA deployment; or use the conditional-forwarder model.
Record added for the wrong site
Cause: Dual-site domains differ (site-a vs site-b).
Fix: Use the correct site suffix.

Task 4 Certificate trust and browser access

Security

Nested VCF consoles present certificates from the VCF default CA. Trusting them properly is both a usability and a security-design point.

Step 1

Open https://vc-mgmt-a.site-a.vcf.lab and inspect the certificate: issuer, subject (FQDN), validity. Do the same for SDDC Manager, NSX Manager and VCF Operations.

Issuer and subject recorded for each console.
Step 2

Download the issuing CA certificate (for vCenter, the VMCA root is available from the vCenter landing page's certificate download link) and import it into your workstation trust store (or browser), then reload the consoles.

vCenter console without a certificate warning; the other consoles noted as trusted or not according to their issuer.
Step 3

Note where VCF 9.0 manages certificates centrally: VCF Operations > Fleet Management > Certificates (configure a CA, replace default certificates, enable auto-renewal) covers ESX, NSX, SDDC Manager, vCenter and the fleet components. For the lab, decide whether to replace the defaults with an internal CA (vcp-admin-06 covers the procedure).

Decision on certificate replacement recorded.
Step 4

Test the webtop's browser path too: the webtop browser inside the HoloRouter network reaches the same consoles; it needs no routing on your workstation but inherits the 9.0.2 unauthenticated-webtop caveat.

Consoles load inside the webtop.
Step 5

Check the SDDC Manager UI deprecation notice and decide which consoles your team uses day to day (VCF Operations and vSphere Client), to limit the certificates you need to trust.

Console list for daily use.
Step 6

Record the risk of permanently trusting lab CAs on a work laptop and your mitigation (separate browser profile, VM, or jump host).

Trust-store risk and mitigation written.
Step 7

Verify SSH host keys for the HoloRouter and a nested host are recorded in your known_hosts and note the Holodeck build phase that bypasses host-key verification (documented 'Force switch' warning) as lab-only behaviour.

Host keys recorded; lab-only behaviour noted.

Validation Gate

Check: Certificates inspected; CA trusted or decision recorded; central certificate management located; webtop path tested; trust-store risk mitigated.

Expected: Clean browser access with a conscious trust decision.

Common Errors

Certificate warning persists after importing the CA
Cause: Browser uses its own store, or you accessed by IP not FQDN.
Fix: Import into the browser store and use the FQDN that matches the certificate.
Trusting each console's leaf certificate individually
Cause: No CA imported.
Fix: Import the issuing CA once.
Lab CA trusted system-wide on a corporate laptop
Cause: Convenience over security.
Fix: Use a dedicated browser profile or a jump host.

Task 5 Multi-workstation and VPN access patterns

Security

One route and one DNS change serve one person. Teams and remote users need a repeatable pattern that keeps the HoloRouter's single-IP exposure model intact.

Step 1

Pattern 1, site router: add the route to 10.1.0.0/20 (and 10.2.0.0/20) via the HoloRouter external IP on the site router, and the vcf.lab conditional forwarder on the site DNS. Every workstation on the site then reaches the lab with no local changes.

Pattern 1 documented with its two configuration points.
Step 2

Pattern 2, jump host: a VM on the external network with the route and DNS set, used over RDP/SSH by everyone; the HoloRouter is reached only from that host. Compare with the webtop (same idea, but unauthenticated in 9.0.2).

Pattern 2 documented; webtop vs jump host compared.
Step 3

Pattern 3, VPN: VPN clients receive the Holodeck routes and the HoloRouter (or site DNS forwarder) as DNS through the VPN configuration; the HoloRouter external IP is never exposed to the internet.

Pattern 3 documented with the route and DNS push.
Step 4

For each pattern list the exposure: which hosts can reach the HoloRouter on 22 and 30000, who can reach nested consoles, and where authentication happens (nested consoles authenticate; the webtop does not).

Exposure matrix for the three patterns.
Step 5

Decide the firewall rules you would apply in front of the HoloRouter external IP for your chosen pattern, and whether the webtop stays enabled.

Firewall rule set and webtop decision.
Step 6

Map the lab access design to production language for the design notebook: management network isolation, jump-host model, DNS delegation, certificate trust distribution.

Design notes written.

Validation Gate

Check: Three patterns documented with configuration points, exposure matrix, firewall rules, webtop decision and design notes.

Expected: A defensible access design for the lab that mirrors production controls.

Common Errors

Exposing the HoloRouter external IP on the internet for remote users
Cause: Convenience.
Fix: Use the VPN pattern; the webtop is unauthenticated.
Per-workstation routes drifting
Cause: No central route.
Fix: Site-router pattern.
VPN users resolve vcf.lab only sometimes
Cause: DNS not pushed via VPN.
Fix: Push the forwarder/HoloRouter DNS in the VPN profile.

Final Validation

The HoloRouter's interfaces, VLAN plan and services are mapped; a workstation reaches the nested estate by a static route and resolves vcf.lab via the HoloRouter or a conditional forwarder; DNS records are managed with the Holodeck cmdlets; certificate trust is handled deliberately; and three access patterns are designed with their exposure.

✓ Architecture → Adapters, VLANs 0/10-25 on 10.1.0.0/20, services, two access paths, appliance map

✓ Routing → Static route via the HoloRouter external IP; bidirectional reachability; flow table

✓ DNS → Lookups via HoloRouter or forwarder; Get/Set/Remove-HoloDeckDNSConfig exercised; reverse lookups

✓ Certificates → Issuers recorded; CA trusted deliberately; central certificate management located

✓ Patterns → Site router, jump host, VPN documented with exposure matrix and firewall rules

✓ Webtop → Decision recorded given the 9.0.2 unauthenticated caveat

✓ Design notes → Lab access mapped to production controls

Cleanup / Restore

Snapshot: holodeck-04-complete

• Remove test DNS records added in Task 3

• Keep the route and DNS configuration you chose

• Record the access pattern decision in the lab notebook

Design Reflection (VCDX)

Access design is a security and manageability conversation: single exposed IP, routed versus jump-host access, DNS delegation, certificate trust distribution, and the authentication boundary (nested consoles authenticate, the 9.0.2 webtop does not). Be ready to translate each lab choice into production equivalents: management network isolation, bastion hosts, conditional forwarders, enterprise CA, and the VCF Operations certificate management that replaces per-console trust.

Requirements

  • Workstations reach nested consoles by FQDN
  • DNS for vcf.lab delegated to the HoloRouter
  • Certificate trust distributed deliberately
  • Access pattern chosen with documented exposure
  • Webtop exposure controlled

Constraints

  • Nested subnets reachable only through the HoloRouter external IP
  • Default VLANs 0,10-25 (Site A) and 40-58 (Site B); /20 CIDRs
  • Webtop unauthenticated in 9.0.2
  • HoloRouter DNS cmdlets take '<ip> <fqdn>' in single quotes
  • Return path depends on the HoloRouter external gateway
  • Site B exists only after a dual-site deployment
  • Custom -DNSDomain changes the nested FQDNs but Holodeck service names stay documented as given

Assumptions

  • Workstation route/DNS rights available
  • Site DNS supports conditional forwarders (Pattern 1)
  • VPN can push routes and DNS (Pattern 3)
  • HoloRouter external gateway reaches the workstation subnet
  • Lab is on a private network
  • No conflicting 10.1.0.0/20 on the external network

Risks

  • Webtop exposed — Impact: unauthenticated lab access — Mitigation: private network or disabled
  • Lab CA trusted on corporate devices — Impact: trust-store pollution — Mitigation: jump host or separate profile
  • Route drift across workstations — Impact: inconsistent access — Mitigation: site-router pattern
  • DNS forwarder loops — Impact: resolution failures — Mitigation: delegate only vcf.lab
  • HoloRouter external IP change — Impact: all routes and DNS break — Mitigation: static IP at OVA deployment
  • Overlapping CIDR with the site network — Impact: routing conflicts — Mitigation: custom /20 CIDR at deployment

Self-Assessment Discussion Prompts

  1. Why does Holodeck's one-external-IP model make the HoloRouter both the gateway and the attack surface, and how do you control it?
  2. When would you choose a site-router route and DNS forwarder over a jump host, and what does each cost operationally?
  3. How does the VCF Operations certificate management change the way you distribute trust compared with trusting each console?
  4. What production control does the unauthenticated webtop violate, and how would you phrase that in a design review?
  5. How would you give remote users access without exposing the HoloRouter, and what must the VPN push?
  6. Where would a custom -DNSDomain help, and what stays on vcf.lab regardless?

Extensions

Conditional forwarder on a Windows DNS server

Implement Pattern 1 end to end with a Windows DNS conditional forwarder for vcf.lab to the HoloRouter and routes on the site router; verify from two workstations.

same

Jump host with the Holodeck route

Build a small Linux jump host on the external network with the route and DNS, and compare its exposure with the webtop.

same

Enterprise CA for the nested estate

Configure a Microsoft CA in VCF Operations > Fleet Management > Certificates and replace the management domain certificates, then remove the lab CA from your workstation.

harder

Custom DNS domain and CIDR

Redeploy the instance with -DNSDomain demo.lab and -CIDR 10.3.0.0/20 and rework the route and forwarder accordingly.

harder

Firewall in front of the HoloRouter

Place a lab firewall before the HoloRouter external IP and implement the rule set from Task 5.

harder

⚠ Known Pitfalls

Routing to the nested subnets without a return path COMMON
Problem: Forward packets arrive, replies never come back.
Resolution: Check the HoloRouter external gateway set at OVA deployment.
DNS records typed without quotes COMMON
Problem: Set-HoloDeckDNSConfig rejects the record.
Resolution: Use -DNSRecord '<ip> <fqdn>' in single quotes.
Relying on the webtop for a team COMMON
Problem: Unauthenticated shared access.
Resolution: Use a routed workstation, site-router or VPN pattern.
Trusting leaf certificates one by one COMMON
Problem: Warnings return after every certificate change.
Resolution: Trust the CA, or replace certificates centrally in VCF Operations.
Overlapping lab CIDR with the office network COMMON
Problem: Routes conflict.
Resolution: Deploy with a custom /20 CIDR.
Switching workstation DNS to the HoloRouter without upstream COMMON
Problem: Internet names stop resolving.
Resolution: Ensure the HoloRouter has an upstream DNS, or use a conditional forwarder.

References

Was this page useful?
Type to search. ↑ ↓ to move, Enter to open, Esc to close.