Recursion Available bit is not set in response header

[xiaoyar]

Version of aardvark-dns

Name        : aardvark-dns
Version     : 1.0.2
Release     : 1.el8
Architecture: x86_64

Configuration

Dual stack network

{
  "name": "dual",
  "id": "2697203bf4180da9e7a6d074e38cbafb2fad4c8a3436522bde4ac573c059caa6",
  "driver": "bridge",
  "network_interface": "podman1",
  "created": "2022-08-24T04:03:37.236675178-05:00",
  "subnets": [
    {
      "subnet": "192.168.227.0/24",
      "gateway": "192.168.227.1"
    },
    {
      "subnet": "fdf8:192:168:227::/120",
      "gateway": "fdf8:192:168:227::1"
    }
  ],
  "ipv6_enabled": true,
  "internal": false,
  "dns_enabled": true,
  "ipam_options": {
    "driver": "host-local"
  }
}

Two containers, foo and bar, resolving bar from foo

[root@foo /]# cat /etc/resolv.conf
search dns.podman
nameserver 192.168.227.1
nameserver fdf8:192:168:227::1

Issue observed

nslookup complains "Got recursion not available from 192.168.227.1, trying next server"

[root@foo /]# nslookup bar
;; Got recursion not available from 192.168.227.1, trying next server
;; connection timed out; no servers could be reached

[root@foo /]#

dig also complains "WARNING: recursion requested but not available"

[root@foo /]# dig bar

; <<>> DiG 9.11.36-RedHat-9.11.36-3.el8 <<>> bar
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 13400
;; flags: qr rd ad; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: b8dbf9748e7ba467 (echoed)
;; QUESTION SECTION:
;bar.				IN	A

;; ANSWER SECTION:
bar.			86400	IN	A	192.168.227.9
bar.			86400	IN	AAAA	fdf8:192:168:227::9
bar.			86400	IN	A	192.168.227.9
bar.			86400	IN	AAAA	fdf8:192:168:227::9

;; Query time: 0 msec
;; SERVER: 192.168.227.1#53(192.168.227.1)
;; WHEN: Fri Aug 26 10:23:45 UTC 2022
;; MSG SIZE  rcvd: 132

[root@foo /]#

[flouthoc]

@xiaoyar Above PR #206 should close this.

[xiaoyar]

@flouthoc I tried with manually applying above PR #206, the issue is not observed any more. Thanks for your quick fix.

[root@foo /]# nslookup bar
Server:		192.168.227.1
Address:	192.168.227.1#53

Non-authoritative answer:
Name:	bar.dns.podman
Address: 192.168.227.5
Name:	bar.dns.podman
Address: fdf8:192:168:227::5

[root@foo /]# dig bar

; <<>> DiG 9.11.36-RedHat-9.11.36-3.el8 <<>> bar
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6759
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: afd65f8137dff79d (echoed)
;; QUESTION SECTION:
;bar.				IN	A

;; ANSWER SECTION:
bar.			86400	IN	A	192.168.227.5

;; Query time: 0 msec
;; SERVER: 192.168.227.1#53(192.168.227.1)
;; WHEN: Wed Aug 31 11:58:56 UTC 2022
;; MSG SIZE  rcvd: 60

[flouthoc]

@xiaoyar Thanks for verifying this should be out in next release.