AnyConnect Android 4.4 (KitKat) Compatibility Update (CSCul28340)

Question

Due to a bug in Android 4.4 (KitKat) reported to Google under Issue #61948, AnyConnect users will experience High Packet Loss over their VPN connection (users will experience timeouts when attempting to access certain network resources). In the ASA logs, a syslog message will appear with text similar to "Transmitting large packet 1420 (threshold 1405)."
This has been reported to Google under Issue #61948
Android 4.4 TCP advertises incorrect MSS over VPN (using VpnService)
https://code.google.com/p/android/issues/detail?id=61948
End users may log in with their Google ID and flag the importance of the request as well as enter comments at the link above.
Conditions:
Android 4.4 (KitKat) including the Google Nexus 5
AnyConnect ICS+
Workaround:
Until Google produces a fix for Android 4.4, VPN administrators may temporarily reduce the maximum segment size for TCP connections on the ASA with the configuration command "sysopt connection tcpmss <mss size>". The default for this parameter is 1380 bytes. Reduce this value by the difference between the values seen in the ASA logs. In the above example, the difference is 15 bytes; the value should thus be no more than 1365. Reducing this value will negatively impact performance for connected VPN users where large packets are transmitted.

Answer 1

Critical issue with DNS resolution on KitKat (4.4.2).
AnyConnect Version 3.0.09242
on Nexus 4
running KitKat (4.4.2).
Firewall config has split-tunnel.
When connected, we CAN reach internal resources but when connected we CANNOT reach external resources.
Ran sniffer to find that DNS requests are having internal DNS search domain appended.
When executing on device:
     $ ping google.com
     ping: unknown host google.com
The sniffer shows:
a faulty DNS lookup for "google.com.example.com" which seems to be appending our search domains to all DNS lookups.
     11:53:45.892635 IP 192.168.124.101.62994 > 192.168.170.133.53: 43772+ A? google.com.example.com.
This problem DOES NOT happen when using KitKat (4.4.2) native IPSec VPN with the same firewall group policy and split-tunnel configuration.
This problem DOES NOT happen for 4.3 (Samsung Galaxy S3) using the same AnyConnect client.