Cronet: Implement DnsConfigWatcher for iOS |
|||||
Issue descriptionImplement DnsConfigWatcher for iOS or disable it all together. The current implementation of DnsConfigWatcher.Watch() method always returns 'false'. This results in the error message "[ERROR:dns_config_service_posix.cc(213)] DNS config watch failed to start."
,
May 12 2016
There's two reasons (I think) we would want this - and not sure if we do. a) If we end up wanting to ship async DNS in Cronet on iOS. I don't know if there's evidence that it's worth doing. b) To detect network configuration changes and flush cached DNS results as well as sockets.
,
May 12 2016
There is also network change watcher/notifier that invalidates the cache when the network changes, e.g. when the user moves from WiFi to Cellular. This should cover most of the cases. However, the user can go to the device "Settings", select "static" network configuration and manually change the DNS. This will probably not trigger the network change event. In that case, the DNS entries in our internal cache will expire in one minute.
,
May 18 2016
kapishnikov@ can you triage?
,
May 18 2016
The DnsConfigWatcher for iOS is a nice feature to have but its absence is not critical. The network change watcher will invalidate the DNS caches whenever the network changes. The scenario that is not covered is when the user manually changes DNS address in the iOS device settings. In that case, an app may use the stale DNS cache entries for up to one minute.
,
Dec 22 2016
Related internal bug: b/33844728
,
May 9 2017
,
Mar 22 2018
,
Jul 16
FYI the benign error message was removed in r567963
,
Jan 2
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by xunji...@chromium.org
, May 12 2016