Verify IPv6 service readiness
Confirm the destination has a stable IPv6 address, the application listens on IPv6, and network rules allow the intended traffic. Check any proxy, firewall, or load balancer in front of the service because DNS alone does not make IPv6 connectivity work.
Test the hostname from networks with IPv6 and compare results with IPv4. Ensure the TLS certificate, virtual-host configuration, and health monitoring cover the same hostname and address family.
Maintain both address families consistently
If the service address changes, update A and AAAA records as appropriate and account for their TTLs. Remove an obsolete AAAA record promptly when IPv6 is no longer served rather than leaving clients to discover the failure.
Monitor IPv6 separately after publishing the record. A successful IPv4 check does not prove the AAAA path is healthy, and a dual-stack client may prefer IPv6 before falling back.