Change to use experiment flags to configure private DNS connect timeout
The previous change aosp/1125321 uses dnsresolver binder service to
set the timeout value. It can complicate the configuration setup when
we provide more than one way to configure the value. The timeout value
is expected to be controllable by the flag only.
Bug: 120182528
Bug: 141218721
Test: atest --include-subdirs packages/modules/DnsResolver
Test: manually set the flag to the device and saw the timeout
was changed
Change-Id: I9b2b566cff3eb7a98162d32ef3716f5c4379b221
diff --git a/ResolverController.cpp b/ResolverController.cpp
index 5fecc61..e690781 100644
--- a/ResolverController.cpp
+++ b/ResolverController.cpp
@@ -210,9 +210,9 @@
if (tlsServers.size() > MAXNS) {
tlsServers.resize(MAXNS);
}
- const int err = gPrivateDnsConfiguration.set(
- resolverParams.netId, fwmark.intValue, tlsServers, resolverParams.tlsName,
- resolverParams.caCertificate, resolverParams.tlsConnectTimeoutMs);
+ const int err =
+ gPrivateDnsConfiguration.set(resolverParams.netId, fwmark.intValue, tlsServers,
+ resolverParams.tlsName, resolverParams.caCertificate);
if (err != 0) {
return err;