Hi,
On Tue, 2014-01-14 at 15:25 +0200, Yevhen Kyriukha wrote:
> I have VPN connection with specified nameservers by VPN server
> (dhcp-option DNS).
> Also I have split routing for VPN connection.
>
> When connection is established name-to-ip resolution for VPN hosts
> works fine, but some time later when I ping host by its FQDN I see
> that wrong (public network) IP is used.
> list-services tells me that I have nameserver for VPN network but
> seems that it's not used.
> Restarting connman solves the problem.
>
> Is there any priority of nameservers in connman?
> Can failures of accessing to some nameservers change priority of using
> nameservers?
It seems there is a minor bug where ConnMan actually ends up using all
nameservers from all networks or nameservers from the wrong service
instead on the nameservers from the default service. Due to a strange
coincidence I noticed the issue yesterday on my system also.
Cheers,
Patrik
_______________________________________________
connman mailing list
[email protected]
https://lists.connman.net/mailman/listinfo/connman