Send connman mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.01.org/mailman/listinfo/connman
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of connman digest..."
Today's Topics:
1. Re: dnsproxy feature doesn't resolve for local domain
(Justin Maggard)
----------------------------------------------------------------------
Message: 1
Date: Thu, 8 Sep 2016 10:08:21 -0700
From: Justin Maggard <[email protected]>
To: Leo Mar <[email protected]>
Cc: [email protected]
Subject: Re: dnsproxy feature doesn't resolve for local domain
Message-ID:
<cakgsxvqx0xnaonfh-tq_7f7+macwmyk89ojmp1cgukjt8rc...@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
I'd guess it's the same issue described here:
https://www.mail-archive.com/[email protected]/msg17355.html
-Justin
On Thu, Sep 8, 2016 at 5:00 AM, Leo Mar <[email protected]> wrote:
> Hi All,
>
> I would like to know whether "search domain option" is being handled from
> connman's internal dns proxy?
> As connman by default runs with dnsproxy enabled, /etc/resolv.conf entries
> will be like below
>
> # Generated by Connection Manager
> nameserver 127.0.0.1
> nameserver ::1
>
> So even domain names got from DHCP server is not added in /etc/resolv.conf.
> But this domain name can be seen in service configuration settings from
> list-services which connman handled internally
>
> Timeservers.Configuration = [ ]
> Domains = [ mydomain.example ]
> Domains.Configuration = [ ]
>
>
> When we try to ping to subdomains in local network, It will not work as
> expected like for example if we have a server "mydomain.example" at
> 192.168.1.10 with a subdomain "myhost.mydomain.example". It is expected to
> "ping myhost" to send it's packages to 192.168.1.10 which is not happening
> in connman. if connman is started with -r option (disable dnsproxy) "ping
> myhost" is working properly.
>
> I have tried using connman 1.25 and now with 1.33 also same behavior.
>
> Can someone help me in explaining is it the expected behavior or an issue in
> connman dnsproxy handling?
>
> Regards,
>
> _______________________________________________
> connman mailing list
> [email protected]
> https://lists.01.org/mailman/listinfo/connman
>
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list
[email protected]
https://lists.01.org/mailman/listinfo/connman
------------------------------
End of connman Digest, Vol 11, Issue 10
***************************************
