The device only supports wifi service. The DNS servers got from ISP through DHCP is
flaky. To make DNS work better, user can specify some backup DNS servers.
And this feature is configurable, by default it is turned off. Only some users
experienced such problem can turn it on.
On Feb 28, 2016, at 11:27 PM, Patrik Flykt
On Fri, 2016-02-26 at 07:52 -0800, Grant Erickson wrote:
> It’s easy to see how this is done one-off, statically for a provision
> or via a per-service-specific configuration setting using
> However, what’s the recommended way to ensure that nameservers can be
> configured, via Nameservers.Configuration, and applied to all
> services, without regard to their technology type or the service name?
> The use case here is that a particular ISP supplies DNS servers in
> DHCP. However, their DNS servers are notoriously flaky and
> non-responsive (i.e. failed average response rate is high).
> Consequently, given how conman’s DNS proxy functions,
> statically-configured servers are a stopgap guarantee that will work
> even when the DHCP-provided servers do not.
So your use case actually continues that all services on the device end
up using the same ISP and it's flaky DNS servers, right?
Usually different WiFi, ethernet and cellular serivces end up using
different ISPs and therefore different DNS servers, leaving only a
subset of the services to be of the flaky kind. For these the option is
to configure them a priori through .config files or after empirical
evidence via D-Bus, as you pointed out.