Hi, Catalin Dominte wrote: > since they [EE] deployed IPv6 in their network (which I think it’s good) I > cannot reach certain destinations that are running on IPv4, because > they go via IPv6 by default.
Have you been able to troubleshoot this more? I thought, based on what I learned in relation to this deployment at UKNOF last year that there was a DNS64/NAT64 mechanism for v4 resources with an appropriate A record, and a 464XLAT mechanism for v4 resources which are 'ipv4 literal' - you are not served a DNS name by the application for the server end of the resource. This should on paper make everything reachable. If it isn't then it may be due to something at the content/application end, and of course the actual 'fix' is to get the content/application end problem sorted. Happy to see another large network deploy v6 to subscribers! A
