joe's questions

The tinydns and dnscache services are running and I have 127.0.0.1 in my resolv.conf:

root@ubuntu:~# cat /etc/resolv.conf 
nameserver 127.0.0.1
domain localdomain
search localdomain

root@ubuntu:~# sv status /etc/service/*
run: /etc/service/dnscache: (pid 927) 22s; run: log: (pid 663) 517s
run: /etc/service/tinydns: (pid 898) 418s; run: log: (pid 660) 517s

root@ubuntu:~# cat /etc/service/dnscache/env/IP
127.0.0.1

root@ubuntu:~# dig @192.168.17.139 joe.com

; <<>> DiG 9.7.1-P2 <<>> @192.168.17.139 joe.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 35794
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;joe.com.           IN  A

;; ANSWER SECTION:
joe.com.        300 IN  A   1.1.1.1

<snip>

Why would I get "WARNING: recursion requested but not available" when running dig. I believe it should be able to recurse using dnscache.

As the title suggests what does "Warning: query response not set" mean. I see the following in the dighost.c (line 2888 and 2889) source but still am uncertain with what in my DNS servers response would cause it.

if (result == ISC_R_SUCCESS && (msgflags & DNS_MESSAGEFLAG_QR) == 0)
    printf(";; Warning: query response not set\n");