Deployment Validation Failure: Invalid NTP and DNS Server Link-Local Address ('169.254.#.#')

Products

• VMware SDDC Manager / VCF Installer

Issue/Introduction

During VCF 9.x/ 5.x, deployment validation or Fleet Lifecycle Management (LCM) pre-checks, the validation engine fails and halts execution with the following fault strings:

• Deployment Validation failed with error: Invalid NTP server provided '169.254.#.#', expecting IP address or FQDN

• Nameserver '169.254.#.#' in DNS Specification is not a valid IP Address or Hostname

Environment

VMware Cloud Foundation (VCF) 9.x, 5.x

vSphere 8.x 

Cause

The IP address 169.254.#.# is an Automatic Private IP Addressing (APIPA) link-local address defined under RFC 3927. It is universally reserved for cloud provider Instance Metadata Services (IMDS) and local node operations.

The VCF installer validation engine performs strict programmatic network pre-checks on all deployment specifications. Core infrastructure dependencies—specifically DNS and NTP—must utilize globally routable corporate network addresses across the Management Domain, Workload Domains, and the VMSP cluster. Link-local addresses are explicitly rejected by the validation engine to prevent unresolvable network states that break Kubernetes cluster bootstrapping, Envoy gateway routing, and Identity Service (IS) JWT time synchronization.

Resolution

To resolve this validation failure, the invalid link-local addresses must be replaced with routable infrastructure addresses.

1. Terminate the active deployment validation task. 

2. Access the VCF deployment specification. 

3. Locate the DNS and NTP configuration arrays.

4. Remove all instances of the 169.254.#.# address.

5. Input valid, routable corporate DNS and NTP IP addresses or Fully Qualified Domain Names (FQDNs).

6. Verify that the provided corporate DNS server infrastructure is properly configured with the necessary forward (A/AAAA) and reverse (PTR) records.

7. Re-execute the deployment pre-checks.