WilliamLam.com

  • About
    • About
    • Privacy
  • VMware Cloud Foundation
  • VKS
  • Homelab
    • Resources
    • Nested Virtualization
  • VMware Nostalgia
  • Apple
You are here: Home / Home Lab / Is a DNS server still required when using a Static IP for VCSA?

Is a DNS server still required when using a Static IP for VCSA?

12.20.2018 by William Lam // 7 Comments

When deploying a vCenter Server Appliance (VCSA), customers have two options for setting up a static network address: using either a hostname (Fully Qualified Domain Name) or just a static IP Address (e.g. no DNS). In the first option when using an FQDN, it should be no surprise that you need to also specify a valid DNS Server which the VCSA UI/CLI Installer will automatically validate both the forward and reverse address. This is the most common deployment model for customers in both production as well as for development environments such as a vSphere home lab.

In the second scenario, where a static IP Address is used, a DNS server is not required because we are NOT using an FQDN for the hostname but rather an IP Address. Having said that, if you have ever used the VCSA UI or CLI, you will find that the DNS Server entry is actually a required field and you can not proceed without providing an address.

VCSA UI Installer:

VCSA CLI Installer:

"network": {
    "ip_family": "ipv4",
    "mode": "static",
    "ip": "192.168.30.151",
    "dns_servers": [
        "192.168.30.1"
    ],
    "prefix": "24",
    "gateway": "192.168.30.1",
    "system_name": "192.168.30.151"
}

As mentioned earlier, we know that it should not be required but currently the VCSA Installer is a bit overly cautious in its pre-checks and does require a value today. This is something that has already been shared internally and the team will be relaxing this requirement in the future.

With that said, this leads us back to the original question posed in the blog title, do we need a valid DNS server when using a static IP for the VCSA?

The answer is no, you do NOT have to provide a valid DNS server address BUT, you can NOT just use a dummy value that is non-reachable on the network. The reason I am bringing this up is that we recently had several customers who had a requirement to deploy several hundred VCSA's in an isolated environment where DNS would not be available. They found some strange behaviors when they had used a non-reachable address for the DNS server input and this caused large delays during the initial setup as well as when rebooting the VCSA. The reason this was happening was that the VCSA tries to perform a lookup of the static IP Address using the provided DNS server, since it was not a working address, it took awhile before the actual operation timed out.

The workaround is actually quite simple and one that I have personally been using since the inception of the VCSA for environments that does not have DNS. Simply use the default gateway address as the value for the DNS entry. When the VCSA tries to perform a lookup, it will fail and return immediately rather than timing out when an invalid address is used instead. Technically speaking, another more reliable address can just be the loop back address (127.0.0.1) which I believe is also the default entry in /etc/resolv.conf but I do not recall 100% off the top of my head.

More from my site

  • Can you really deploy the vCenter Server Appliance (VCSA) without DNS and NTP?
  • Using PowerCLI to automate the retrieval of VCSA Identity Sources
  • How to deploy the vCenter Server Appliance (VCSA) with a custom MAC Address?
  • How to exclude VCSA UI/CLI Installer from MacOS Catalina Security Gatekeeper?
  • Using PowerCLI to automate the retrieval of VCSA Password Policies

Categories // Home Lab, VCSA Tags // dns, vcenter server appliance, VCSA

Comments

  1. *protectedVavai says

    12/20/2018 at 2:18 pm

    Acccording to use a non lookup address and experience some strange behaviour, is this possible to simply add the address on /etc/hosts so host will take the records from /eyc/hosts instead of DNS Records?

    Reply
  2. *protectedAadil Mir says

    12/21/2018 at 1:52 am

    Yep , that works fine .

    Reply
  3. *protectedTom Kuhn says

    04/02/2019 at 12:11 pm

    I am currently trying to perform this same thig and am having a lot of issues getting this to work. I currently have a standalone network without a gateway. The network is 192.168.150.50 (vCenter IP), .51 (ESXi#1), .52 (ESXi#2). The installer will not allow 127.0.0.1. Everything installs fine if I startup a simple DNS, but I am not sure what to point the DNS to if I do not have an actual gateway.

    Reply
  4. *protectedVijay Rajput says

    12/06/2019 at 4:15 am

    Nice blog. I understood the concept very well. This blog is very informative. And it's very interesting topic. Visit to get more knowledge. How To Upgrade Esxi Server To 6.7 On HP Proliant DL380 Gen9 Server https://www.hex64.net/how-to-upgrade-esxi-server-to-6-7-on-hp-proliant-dl380-gen9-server

    Reply
  5. *protectedMatt says

    01/16/2020 at 3:11 am

    Thanks for clarifying this, it's been really helpful. However, I've raised a ticket for an unrelated issue and VMware won't investigate it as they say deploying a vCenter by IP is unsupported. I can't find this documented anywhere but do you know if this is now the case?

    Reply
  6. *protectedRM says

    08/15/2020 at 11:29 am

    VCSA runs dnsmasq... Seems like it'd be fairly simple to leverage it as a full DNS server in a lab environment.

    Reply
  7. *protectedjecogiteRodolphe says

    04/15/2023 at 2:17 pm

    Hello

    In VCSA 8, in the template there is an element we don't see in your tuto.
    What are we supposed to fill ?

    "new_vcsa": {
    "vc": {
    "__comments": [
    "'datacenter' must end with a datacenter name, and only with a datacenter name. ",
    "'target' must end with an ESXi hostname, a cluster name, or a resource pool name. ",
    "The item 'Resources' must precede the resource pool name. ",
    "All names are case-sensitive. ",
    "For details and examples, refer to template help, i.e. vcsa-deploy {install|upgrade|migrate} --template-help"

    Reply

Thanks for the comment!Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Search

Thank Author

Author

William is Distinguished Platform Engineering Architect in the VMware Cloud Foundation (VCF) Division at Broadcom. His primary focus is helping customers and partners build, run and operate a modern Private Cloud using the VMware Cloud Foundation (VCF) platform.

Connect

  • Bluesky
  • Email
  • GitHub
  • LinkedIn
  • Mastodon
  • Reddit
  • RSS
  • Twitter
  • Vimeo

Recent

  • VMware Flings is now available in Free Downloads of Broadcom Support Portal (BSP) 05/19/2025
  • VMUG Connect 2025 - Minimal VMware Cloud Foundation (VCF) 5.x in a Box  05/15/2025
  • Programmatically accessing the Broadcom Compatibility Guide (BCG) 05/06/2025
  • Quick Tip - Validating Broadcom Download Token  05/01/2025
  • Supported chipsets for the USB Network Native Driver for ESXi Fling 04/23/2025

Advertisment

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here: Cookie Policy

Copyright WilliamLam.com © 2025

 

Loading Comments...