>> If I do that, I can see that the current way of stripping the domain name >> from reply is broken in forward_dns_reply() as it does not really strip out >> the domain name part: >> >> tcpdump (lo): >> IP (tos 0x0, ttl 64, id 36270, offset 0, flags [DF], proto UDP (17), length >> 48) >> 127.0.0.1.33898 > 127.0.0.1.53: 10971+ A? bz. (20) >> IP (tos 0x0, ttl 64, id 36271, offset 0, flags [DF], proto UDP (17), length >> 82) >> 127.0.0.1.53 > 127.0.0.1.33898: 10971 1/0/0 bz.siirappi.com. A 1.2.3.4 >> (54) >>
>We could optimize the resolver a bit so that if the DNS server returns >not found for a query, we could wait until we get a "name found" >response before returning something to the client. Would you like to >investigate this more and send a patch? As stated on the other thread my analysis was bit wrong, however the patch which I sent fixes the problems when hostname queried is a valid domain tld. However the other problem still exists, forward_dns_reply() does not strip the domain name part away from the answer-block (as discussed on IRC) which will lead to fails. Br, Pasi _______________________________________________ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
