Hi,
On Thu, 2012-07-19 at 15:25 +0200, Erik Bernoth wrote:
> On the target, the machine using ConnMan (and without "search" or
> "domain" in the resolv.conf), "ping sub" will request "sub" and the
> response will be the same as on my Ubuntu machine, just without the
> appended "internal-server".
resolv.conf should only contain a 'nameserver 127.0.0.1' entry, nothing
else. This seems to be the case here, as 'ping sub' doesn't resolve
anything.
> So he asks for "sub" and he recieves a
> correct IP adress, but everywhere there is no "sub.internal-server".
resolv.conf should not be modified. Search domains must be set in
Domains.Configuration for the service service in question. See the
Domains.Configuration property description in doc/service-api.txt.
> There are also some additional RR's in the end which can't be read
> correctly by wireshark. I tested that in many different variations and
> many times, so I am sure that is always the case. The ping will still
> fail, with telling that "sub" is unknown.
I have seen wireshark reporting garbage here too. Nothing affecting the
DNS lookup, though. Do you see this on the upstream wire or on the
loopback interface?
> This is confusing, because on one side he recieves the correct
> information (the IP adress) and doesn't use it, on the other hand he
> asks for the wrong thing ("sub" and not "sub.internal-server") and
> still gets a response instead of a "No such name" as on the other
> computers. Last but not least only in this scenario the DNS response
> seems to be broken.
I can't deduce what your setup is in this part. Do not touch resolv.conf
after ConnMan is started and add a suitable Domains.Configuration to the
service with test/set-domains python script. If it still doesn't work,
please provide the contents of resolv.conf, the properties for this
service with test/list-services and the tcpdump output for DNS lookups
on the target with Domains.Configuration being set and not set.
Cheers,
Patrik
_______________________________________________
connman mailing list
[email protected]
http://lists.connman.net/listinfo/connman
