Hi Erik,
On 07/18/2012 03:06 PM, Erik Bernoth wrote:
Hi Marcel,
thanks for your reply!
2012/7/18 Marcel Holtmann <[email protected]>:
Hi Erik,
actually ConnMan creates a local DNS proxy and cache at localhost. And
it should put 127.0.0.1 nameserver in /etc/resolv.conf. The -r option
forces ConnMan to disable the DNS proxy.
So what you are talking about is the search domain option. And we are
not doing that via our internal DNS proxy?
Regards
Marcel
Without "-r" ConnMan writes 127.0.0.1 as nameserver in the
/etc/resolv.conf, as you say. And it resolves domains like gogle.com,
but it doesn't resolve subdomains in the local network, even though
ConnMan knows the domain name (see "list-services" result in the first
message)
normal start-up /etc/resolv.conf:
# Generated by Connection Manager
nameserver 127.0.0.1
-> "ping google.com" works
-> "ping sub" doesn't work
after udhcpc -i eth1:
domain internal-server
nameserver 192.168.1.1
-> "ping google.com" works
-> "ping sub" works(!!)
after hadware reset starting with /usr/sbin/connmand -n -r:
# Generated by Connection Manager
search internal-server
nameserver 192.168.1.1
-> "ping google.com" works
-> "ping sub" works, too
There have been some fixes to resolver regarding search domain handling
in May after your commit 6d6f312fb2b751b4cf70. Could you try to upgrade
in order to see if your problems are solved already?
Cheers,
Jukka
_______________________________________________
connman mailing list
[email protected]
http://lists.connman.net/listinfo/connman
