Which action fixes the DNS/address publishing issue after an SVM failover?

Which action fixes the DNS/address publishing issue after an SVM failover?

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

Answer: (A)

Dynamic DNS updates on the SVM ensure that DNS records reflect the SVM’s current IPs after a failover. When an SVM fails over, its IPs (VIPs) can move to another node. If DNS isn’t refreshed, clients may resolve to the old, now-unused addresses. Enabling dynamic DNS updates lets the SVM automatically push the correct A (and PTR) records to the DNS server, so name resolution stays accurate and access remains uninterrupted. The other options don’t address DNS publication. LIF auto-rebind helps keep traffic directed to an available LIF but doesn’t update DNS records. Export policies affect NFS/SMB access control, not DNS publishing. FlexCache is a caching feature and doesn’t fix DNS address publication after failover.

Dynamic DNS updates on the SVM ensure that DNS records reflect the SVM’s current IPs after a failover. When an SVM fails over, its IPs (VIPs) can move to another node. If DNS isn’t refreshed, clients may resolve to the old, now-unused addresses. Enabling dynamic DNS updates lets the SVM automatically push the correct A (and PTR) records to the DNS server, so name resolution stays accurate and access remains uninterrupted.

The other options don’t address DNS publication. LIF auto-rebind helps keep traffic directed to an available LIF but doesn’t update DNS records. Export policies affect NFS/SMB access control, not DNS publishing. FlexCache is a caching feature and doesn’t fix DNS address publication after failover.