When upgrading from NSX 3.2.2 to 4.x, the display name of the default DNS service (TCP/53) is not automatically updated to DNS-TCP

Products

• VMware vDefend Firewall
• VMware NSX Firewall
• VMware NSX

Issue/Introduction

In NSX-T 3.x releases, two default DNS services are available under Inventory:

1. DNS-UDP – Service entry with destination port 53 and protocol UDP.
2. DNS – Service entry with destination port 53 and protocol TCP.

 

Starting with NSX 4.x releases, the display name of the default DNS service (TCP/53) has been updated to DNS-TCP for improved clarity and consistency.

Note: This is only a display name change. The service’s policy path and UUID remain unchanged.

 

Greenfield Environments:

In fresh deployments with NSX 4.x, the display name change from DNS to DNS-TCP is applied by default. Additionally, several new DNS services are introduced as part of feature enhancements.

 

 

Brownfield Environments:

When upgrading from NSX 3.1, 3.2.0, or 3.2.1 to 4.x, the migration task in the upgrade workflow automatically updates the display name of the default DNS (TCP/53) service to DNS-TCP.

Important Note for Upgrades from NSX 3.2.2 to 4.x : In this upgrade path, the migration task does not run, and the display name remains as DNS. Manual intervention is required to update the service name.

 

Environment

NSX-T 3.2.2 releases

Cause

During an upgrade from NSX 3.2.2 to 4.x, the migration task responsible for renaming the service from DNS to DNS-TCP is not triggered, leaving the display name unchanged.

 

Resolution

If you encounter this scenario, please reach out to Broadcom Support for assistance.