You seem to be working on the assumption that the Internet Sharing-based DNS64/NAT64 test network requires IPv6 connectivity. That’s not the case. In fact, if you deploy it on a network with IPv6 connectivity, it won’t use that (r. 24142384). There’s a bunch of complexity here, so let’s start from fundamentals.
From the client device’s perspective there are three types of networks to consider:
-
IPv4-only (A)
-
IPv4 and IPv6, aka dual stack (B)
-
IPv6-only, using DNS64/NAT64 to get at IPv4 servers (C)
Type A is the status quo. Type B is your current office setup (IPv4 and IPv6 are peers). Type C is the expected deployment network that App Review cares about.
The Internet Sharing-based DNS64/NAT64 test network is not an exact match for any of these. The IPv6 Connectivity section of my IPv6 and App Review post explains this difference.
Given that, hanging the Internet Sharing-based DNS64/NAT64 test network off your dual stack office network is kinda pointless; the test network won’t use the IPv6 connectivity that your network provides.
Finally, I should stress that the vast majority of problems that we see where an app works in the Internet Sharing-based DNS64/NAT64 test network but fails in App Review relates to DNS. DNS64/NAT64 network walks a DNS path that’s rarely used (it requires that the DNS say “No” in the correct way) and App Review’s DNS64/NAT64 gateway is less forgiving that it should be. My IPv6 and App Review post explains this in more detail, and shows how you can look for DNS problems like this.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"