Failed to fetch DNS Forwarder status/statistics occasionally, and persists once triggered

Products

• VMware NSX

Issue/Introduction

• After creating a DNS Forwarder service, the 'GET status/statistics' API call for DNS Forwarder may fail with error messages.
• However, no DNS Forwarder DOWN alarm is reported, and the DNS Forwarder continues to function normally.
• When logging in to the DNS Forwarder edge node as root, the /var/log/dns/cli.log file doesn't exist.
• Below log-lines may be seen at NSX Edge syslog:

2025-09-08 04:22:56,846 ERROR vmware.common.nsxsdk_helpers:log_api_call_details [MainThread] - HTTP Status Code: 400 and HTTP Response Body: {
  "httpStatus" : "BAD_REQUEST",
  "error_code" : 504022,
  "module_name" : "Policy",
 "error_message" : "Unable to get the statistics of path=[/global-infra/tier-1s/Tier1###########/dns-forwarder] from enforcement point path=[/global-infra/sites/######/enforcement-points/default]. Error: Node #######a3 status is ERROR, DNS forwarder statistics are incomplete."

Environment

VMware NSX 9.0.1

Cause

The /var/log/dns/cli.log file fails to generate, causing subsequent GET API calls via the CLI to fail.

Resolution

Log in to the edge admin CLI and then run

> get dns-forwarder status

The CLI triggers generating the cli.log successfully. After that, the GET status/statistics API should work.

Additional Information

The datapath is not impacted by this problem.