We are currently having an issue in the org I support in which the Citrix Netscaler VPN Client is causing the local home LAN IP (ususally a 192.168.* IP) to register a forward lookup zone record for that client machine with that IP. We are still working through the troubleshooting of this issue, but it causes the following behavior.
1. Creates a dynamic A record in the forward lookup zone with the 192.168.* address for the laptop.
2. No PTR record is created since it is not an internal IP.
3. While this is occurring, users are complaining that Outlook cannot connect to Exchange 2013 on-prem.
We have someone that is convinced that Exchange needs the PTR record to maintain Outlook connectivity. However, I can find no documentation for this anywhere, and no breakdown of the Outlook 2016 client and how it uses DNS during the connection process. I do not believe a lack of PTR record in the reverse lookup zone for the laptop connecting via VPN is necessary, and that this is a "red herring."
My main question is: Does a client machine PTR record matter for Exchange connectivity? Is there any documentation our there that I missed that shows how DNS is utilized in the connection between Outlook and Exchange on-prem?