There came a up a question that is it possible to share data between two DA clients through DA-connection. I did some research on couple of Server 2012 based DA-environments and found out that client 1 cannot resolve a name of client 2 even it has registered it's IPv6 address. And the situation is the same in both environments and with other clients too. So I assume this is some how related into DA name resolution behaviour. Is there any explanation why clients names cannot be resolved if resources are IPv6 based (In this case IP-HTTPS clients)? Is this maybe a limitation related to NAT64/DNS64? Should connectivity between clients even work?
Yes, communication between DA clients is possible. As long as your internal DNS is accepting the DA clients registrations of their IPv6 addresses, they should be able to resolve each other. Sometimes I see that DNS blocks the AAAA registrations, and then of course if those machines are not in DNS, they aren't going to be resolvable. So yes, usually DA clients can resolve each other's names. Contacting them is a more involved story, because it involves making sure that the right firewall rules are in place on the clients to allow things like file access and RDP to work, but as long as the rules are allowing the right kinds of communications from the right prefixes (the IP-HTTPS prefix in your case), then it should work.
- Proposed as answer by Alex LvMicrosoft contingent staff, Moderator Friday, December 20, 2013 8:36 AM
Yes, you can, total agree with Jordan Krause. In short, the DA service just like the legacy VPN, the server name can be resolute with your internal DNS.
Hope this helps.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.