During SVM failover, DNS records do not update and clients connect to old IPs. What action fixes this issue?

During SVM failover, DNS records do not update and clients connect to old IPs. What action fixes this issue?

• A. Enable LIF auto-rebind
• B. Set dynamic DNS updates on the SVM
• C. Change export policies
• D. Add FlexCache

Answer: (B)

When a failover moves a LIF to a different node, its IP address can change, and clients rely on DNS to reach that LIF. If DNS isn’t updated, clients keep resolving to the old IP, leading to failed connections until DNS TTL expires. Enabling dynamic DNS updates on the SVM lets the system automatically push the new LIF IPs into the DNS zone (and update PTR records as needed), so DNS always points to the current addresses after failover. This requires a DNS server that accepts dynamic updates and proper permissions for the SVM to update records. Other options don’t address the need to refresh DNS records after IP changes: LIF auto-rebind moves the LIF but doesn’t automatically update DNS; export policies govern access to exports, not DNS; FlexCache is a caching feature and won’t fix DNS update behavior.

When a failover moves a LIF to a different node, its IP address can change, and clients rely on DNS to reach that LIF. If DNS isn’t updated, clients keep resolving to the old IP, leading to failed connections until DNS TTL expires. Enabling dynamic DNS updates on the SVM lets the system automatically push the new LIF IPs into the DNS zone (and update PTR records as needed), so DNS always points to the current addresses after failover. This requires a DNS server that accepts dynamic updates and proper permissions for the SVM to update records.

Other options don’t address the need to refresh DNS records after IP changes: LIF auto-rebind moves the LIF but doesn’t automatically update DNS; export policies govern access to exports, not DNS; FlexCache is a caching feature and won’t fix DNS update behavior.