DNS of container does not get updated when the DNS on the network is changed

Welcome to Cohesity Documentation.

Ask me anything. From setup and configuration to troubleshooting, architecture, features, and release updates, I'm here to help.

AI may make mistakes. Always verify critical information.

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products

Data Security Alliance

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products

Data Security Alliance

DNS of container does not get updated when the DNS on the network is changed — NetBackup Flex Scale 3.0 | Cohesity Documentation

Home

Veritas NetBackup™ Flex Scale Release Notes

Known issues

Networking issues

DNS of container does not get updated when the DNS on the network is changed

Veritas NetBackup™ Flex Scale Release Notes · PDF

Download PDF

When a new DNS server is added to the configuration, the containers do not become aware of it. Only the hosts know about the new DNS server. (IA-24663)

Workaround:

Stop and start each node one by one. This way the containers are restarted and they pick the updated resolve.conf file from the host. This causes job failures and jobs may or may not get automatically restarted based on the associated policy.

Feedback

Was this page helpful?

Networking issues

Cluster configuration workflow may get stuck

Feedback

Was this page helpful?