We first identified this issue about a month ago when users could not get access to external/internet websites. Upon investigating the issue we confirmed that the users were getting the IP address assigned from BIG-IP. However, when confirming this address with our Windows DNS we found that certain users were registered with their 192.168.x.x address. F5 Support recommended that we create an additional DNS zone for the remote users using the Edge client. We done so and also made the change in BIG-IP to reflect the new DNS suffix. However, this did not made any difference to how the client connected to our network. The client connected using the same DNS suffix as before and ignored the new DNS zone that we created for it. We even deleted the DNS suffix from BIG-IP and the Edge client connected as normal. This left us a bit confused as to why this would not as least stop the Edge client from successfully connecting to our network. We have spoken to F5 Support at create length regarding this behavior and are awaiting further assistance.
The initial post is from 2017 and I am concerned that this issue hasn't been answered from someone from F5 Support. Are we able to ask for someone at F5 Support to provide any assistance with this? Its odd that this problem is happening in more than one environment and nobody has an answer why or how to resolve it.