Yes, I have seen issue #1 (DNS suffix). In fact, we noticed it because after the connection is disconnected, the concentrator's default suffix remains behind on the client.
This was okay for company equipment, because their default suffix was the same, but for home/remote users, this overrode their default "DNS suffix for this connection" setting causing them problems.
We found if we set the "Append these DNS suffixes" with their default suffix, Cisco VPN still overrides this, but when the connection is terminated, they have their old default suffix back. So only during a VPN session will there be a problem resolving local suffixes.
Good to know that others are also having this problem, I haven't seen a caveat from cisco regarding this. Our main problem is with home/remote users. Local domains are not being resolved, unless the fully qualified name is typed in.
Can someone in Cisco comment on this problem ? This problem alone is stopping us from rolling out v4 client.
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...