On 27.10.2015 15:00, SpiderX wrote: > ~ $ host -v nefrit1 > Trying "nefrit1" > Host nefrit1 not found: 3(NXDOMAIN) > Received 100 bytes from 127.0.0.1#53 in 0 ms > > So, we have two queries to two nameservers. Two of them have returned > NXDomain, and this result was sent back to a client. > I think this behaviour is wrong, client shouldn't get NXDomain when > other non-nxdomain replies from nameservers exist. > > This was fixed once (see commit > http://git.kernel.org/cgit/network/connman/connman.git/commit/src/dnsproxy.c?h=1.30&id=0439194ed0c5a90f61dbef86d9a51307764da2d7), > but then was refactored in later commits
I'm able to reproduce the issue. However it seems that connman's dnsproxy properly caches the response, so if I do "host -v -t a bz" immediately after the first query there will be a proper response. Though, it would be nice if it would work also when the response is not in the cache. I will try to check what broke it.. First try: host -v -t a bz Trying "bz" ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44260 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;bz. IN A Received 20 bytes from 127.0.0.1#53 in 122 ms Second try: host -v -t a bz Trying "bz" ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26675 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;bz. IN A ;; ANSWER SECTION: bz. 49 IN A 1.2.3.4 Received 38 bytes from 127.0.0.1#53 in 7 ms Br, Pasi _______________________________________________ connman mailing list [email protected] https://lists.connman.net/mailman/listinfo/connman
