WilliamLam.com

  • About
    • About
    • Privacy
  • VMware Cloud Foundation
    • VMware Cloud Foundation 9.1
    • VMware Cloud Foundation 9.0
  • VKS
  • Homelab
    • Hardware Options
    • Hardware Reviews
    • Lab Deployment Scripts
    • Nested Virtualization
    • Homelab Podcasts
  • VMware Nostalgia
  • Apple
You are here: Home / NSX / Quick Tip - NSX Edge fails DNS pre-check as part of VCF 9.0.2 Upgrade

Quick Tip - NSX Edge fails DNS pre-check as part of VCF 9.0.2 Upgrade

01.23.2026 by William Lam // Leave a Comment

As I continue my VMware Cloud Foundation (VCF) 9.0.2 upgrade journey, I have now reached the core SDDC components, including vCenter, NSX, and ESX.


NSX Manager and NSX Edges was up first and before the upgrade begins, a pre-check is performed. I was not expecting any issues but to my surprise, I ran into the following validation error:

DNS is not configured on edge 83ea6662-41b2-48aa-a8d0-22039d3230c0. Edge will not be able to resolve the fqdn to download the upgrade bundle from NSX manager. Kindly configure a valid DNS on edge.. Other components that failed with the same error: edge01b, edge01a


We all know how important DNS is and ensuring it is configured correctly, both forward and reverse lookups.

However, I like to think that I am pretty good about ensuring everything in my lab is setup with DNS and this honestly was a surprising error, that BOTH NSX Edges do NOT have DNS configured!?! 🤔

I logged into one of my NSX Edges using the admin account and using the get name-servers and get search-domains commands, sure enough nothing was configured!


The fix was quite easy by using the set name-servers and set search-domains command and then quick ping for a known FQDN to ensure DNS lookup was successful.


After chatting with some folks internally, they too confirmed they have seen the same behavior as part of upgrade.

It turns out DNS configuration for NSX Edges is NOT a required input, at least when using the Simplified Edge Deployment within vCenter Server, which is exactly how I had deployed these Edges. At least, it was not user error 😅

I will file a product enhancement if one has not already been filed since DNS is indeed critical for NSX Edge during upgrade as they will need to fetch the bundle updates which will be pulling from an FQDN.

Categories // NSX, VMware Cloud Foundation Tags // VCF 9.0

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

  • VCF 9.1 - Quick Tip: Forgot to Retrieve Auto-Generated Passwords from VCF Installer? 06/09/2026
  • VCF 9.1 - Configuring vSphere Supervisor to use VCF Identity Broker (IDB) for External Identity Federation 06/08/2026
  • VCF 9.1 - Quick Tip: Understanding VCF Installer Default Behavior for VCF Patch Releases 06/07/2026
  • VCF 9.1 - Quick Tip: Upgrading ESX Hosts with Non-Certified vSAN ESA NVMe Devices in SDDC Manager 06/06/2026
  • VCF 9.1 - Deploying VCF Automation (VCFA) to non-Management Network 06/05/2026
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 © 2026

Loading Comments...