Configure the server for compatibility with IPv6 (for the API used by the rejected iOS application)

Question

I understand that there are already a lot of questions about stack overflow for users who have disabled iOS apps from Apple, because they do not work on the network only with IPv6.

I already checked my code to make sure that there are no hard-coded IP addresses (definitely not) and that old accessibility (none at all) or other low-level network environments are used (we use only NSURLSession). I went through the NAT64 test network on my machine, and the application (appeared) worked fine.

This is a Xamarin application that communicates with the API via HTTPS (and no other network connections).

Some of the answers found showed that a solution to this problem requires configuration changes on the server.

So my overall question is, what configuration changes are required? In particular, do you need an AAAA record in a domain? If so, how to configure it?

I come to this problem more as a software developer, so without a detailed understanding of how IPv6 works and what server changes are required.

Answer 1

Unable to change your server. NAT64 should take care of translation only for IPv4-enabled servers, and DNS64 should make sure that you get the correct address for the host name. Therefore, when you use hostnames, not hard-coded addresses, and you use API versions that are neutral with respect to the IP version, then this should usually work.

, , - Apple DNS // AAAA. DNS- DNS64, , IPv6 .

DNS64, MacOS, "" IPv6 AAAA, DNS64 . , , , Apple , .

, - DNS64 NAT64 https://nat64check.org/. .

, -, IPv6 AAAA. NAT64 DNS64, . IPv6, , - , IPv4 (, CGN, DS-Lite ..).

DNSSEC: NAT64 "" AAAA, IPv6, DNSSEC , DNS. AAAA, NAT64 , DNSSEC .

: IPv6 DNS AAAA. . AAAA (, , ::ffff:, 2001:db8:, 64:ff9b:, fc fd). , IPv6, . IPv6, .