Hans Dedecker writes:
> Hi Felix,
>
> Current implementation in netifd writes the dns servers into
> resolv.conf.auto file based on the order of the interfaces in the
> interface list which is alphabetical sorted. The resolver, in this
> case dnsmasq, reads the resolv.conf.auto file and queries t
On Mon, Sep 5, 2016 at 1:49 PM, Jo-Philipp Wich wrote:
> Hi Hans,
>
> imho it would also make sense to take any existing metric setting into
> account as well. At least I'd expect that if I have a wan1 with metric
> 10 and a wan2 with metric 20 that the DNS server entries "inherit" the
> same weig
Hi Hans,
imho it would also make sense to take any existing metric setting into
account as well. At least I'd expect that if I have a wan1 with metric
10 and a wan2 with metric 20 that the DNS server entries "inherit" the
same weight/order.
So priority wise I'd first order by dns metric, then by
On 2016-09-05 10:45, Hans Dedecker wrote:
> Hi Felix,
>
> Current implementation in netifd writes the dns servers into
> resolv.conf.auto file based on the order of the interfaces in the
> interface list which is alphabetical sorted. The resolver, in this
> case dnsmasq, reads the resolv.conf.auto
Hi Felix,
Current implementation in netifd writes the dns servers into
resolv.conf.auto file based on the order of the interfaces in the
interface list which is alphabetical sorted. The resolver, in this
case dnsmasq, reads the resolv.conf.auto file and queries the
nameserver(s) in the order liste
