"Too many DNS servers configured" warning in Aria Operations after DNS update

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• Updating DNS via vApp properties in Aria Operations fails to resolve correctly. The OS displays a mix of old and new IP addresses, triggering a "Too many DNS servers configured" warning.

Environment

VMware Aria Operations 

Cause

Legacy DNS IPs are hardcoded in the global /etc/systemd/resolved.conf file. The systemd-resolved service incorrectly aggregates these legacy IPs with the newly provisioned interface IPs from /etc/systemd/network/10-eth0.network. This causes the total DNS count to exceed the system limit of three, breaking resolution.

Resolution

Manually remove the legacy DNS entries from the global resolver configuration:

1. SSH into the Aria Operations node as root.

2. Edit the global resolver file:

   vi /etc/systemd/resolved.conf

3. Locate the DNS= line containing the legacy IPs under the [Resolve] section.

4. Delete or comment out (#) the entire line.

5. Save and exit (Esc, :wq, Enter).

6. Restart the resolver service:

   systemctl restart systemd-resolved

7.  Verify the output now only shows the correct IPs:
   

   cat /run/systemd/resolve/resolv.conf

Additional Information

This aligns with the documented networking behavior for Aria appliances detailed in Broadcom KB 315960: Modifying the DNS settings of Aria Operations for Logs