On Feb 26, 2016, at 1:57 AM, connman-request(a)lists.01.org wrote:
On Thu, 2016-02-25 at 10:52 -0800, wangfe-nestlabs wrote:
> Background information.
> Connmand will not use fallback name servers when some name servers are
> provided by DHCP reply. But in some cases, the ISP provided its own
> name servers can?t be down, then DNS won?t work. So some requirement
> is to use some fallback name severs such as 220.127.116.11, 18.104.22.168 for
> Add the option flag ?AlwaysUseFallbackNameservers?. Which it is
> enabled, the fallback name servers are appended to name server list,
> and will be used. The duplicate servers will be filtered out in the
NACK. FallBackNameservers are just that, a list of servers to use when
there are zero nameservers provided otherwise. Every service has already
a Nameservers.Configuration attribute which takes precedence over the
ones provided by DHCP.
It’s easy to see how this is done one-off, statically for a provision or via a
per-service-specific configuration setting using Nameservers.Configuration.
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.