<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Cloud Builder on DimensionQuest - Burke's Blog!</title><link>https://dimensionquest.net/tags/cloud-builder/</link><description>Recent content in Cloud Builder on DimensionQuest - Burke's Blog!</description><generator>Hugo</generator><language>en-us</language><copyright>Copyright © 1999-2026 Burke Azbill. All Rights Reserved.</copyright><lastBuildDate>Sat, 30 Nov 2024 17:33:34 +0000</lastBuildDate><atom:link href="https://dimensionquest.net/tags/cloud-builder/index.xml" rel="self" type="application/rss+xml"/><item><title>Home Server Build for VMware ESXi and Holodeck</title><link>https://dimensionquest.net/2024/11/home-server-build-for-vmware-esxi-and-holodeck/</link><pubDate>Sat, 30 Nov 2024 17:33:34 +0000</pubDate><guid>https://dimensionquest.net/2024/11/home-server-build-for-vmware-esxi-and-holodeck/</guid><description><![CDATA[<p>When working with a Holodeck environment, a pretty beefy system is required. While you can get vSAN Ready nodes from vendors like SuperMicro, Dell, HP, etc&hellip; I chose to DIY because I really enjoy building systems and wanted something more home-friendly (Read: Less power hungry and quieter.) I&rsquo;ll do a more in-depth post soon, but for now I&rsquo;ve had a number of request for my Bill Of Materials (BOM) for my new server.</p>]]></description><enclosure url="https://dimensionquest.net/2024/11/home-server-build-for-vmware-esxi-and-holodeck/images/holodeck-diagram.png" length="169496" type="image/png"/></item><item><title>How to update upstream DNS servers in Holodeck Cloud Builder</title><link>https://dimensionquest.net/2024/10/holodeck-upstream-dns/</link><pubDate>Thu, 03 Oct 2024 17:33:34 +0000</pubDate><guid>https://dimensionquest.net/2024/10/holodeck-upstream-dns/</guid><description>&lt;p>When working with a Holodeck environment, the Cloud Builder VM acts as DNS for the lab environment. This handles all dns resolution within the lab itself and forwards all non-lab related DNS queries to upstream DNS servers. These servers are defined VMware Cloud Foundation Lab Constructor (VLC) during the intiial deployment of the lab environment. I needed to do this recently in a lab environment that I moved from one cloud to another, where the originally specified upstream DNS Servers no longer existed. Having invalid upstream DNS Server specified results in extended time to resolution and/or failed requests to resources that reside outside of the Holodeck lab environment.&lt;/p></description><enclosure url="https://dimensionquest.net/2024/10/holodeck-upstream-dns/images/holodeck-diagram.png" length="169496" type="image/png"/></item></channel></rss>