When our AnyConnect clients connect remotely, they get a 172.a.b.c address from our ASA and register this address with our DNS server, so everything is good... until they get back into the office.... when the client later boots up onto the corporate LAN, it then gets a new 10.a.b.c address form DHCP, BUT this address does not get updated in its host record in DNS. Oddly, the reverse entry is correct.
Any idea whats going on here and how to correct it? Is this a Windows issue, AC issue or DNS issue?
Thanks in advance.
John
