We are having a strange issue that appears to be caused with our split-dns setup. When users connect to the ISA VPN, they maintain the old address in local cache, at least for a bit. This is causing mail connection issues, since that IP uses private internally, and public externally.
I thought when VPN clients connect to ISA they automatically flush the local dns cache, but this issue is apparently highlighting that not to be the case. Is there anything I can check to determine if it is working, or if not, to force a client to simply run a script to do that? I've never forced any scripts over or after an ISA VPN connection so if that's the case I need details on how that is done.
ISA 2006 via Server 2003
Connecting clients are Windows XP
VPN type is PPTP, NO split-tunneling, all traffic through the tunnel
Mail server type is Exchange 2010 (recently changed from 2007)
DNS hosted on Server 2008, split internally (private addressing) versus externally (public addressing hosted on different servers)