No ad-flag with pihole/unbound

[Falconcrest]

Could it be that since the last update of Pihole (Core, FTL, Web) when using unbound with e.g.

dig google.com @127.0.0.1 -p 5335

no ad-flag is displayed anymore?

Can anyone verify this?

All my pihole/unbound installations are currently like this.
Since I don't check it constantly, I know it has been working correctly this year.

[deHakkelaar]

@Falconcrest

Can anyone verify this?

Old Raspi still running v5:

$ hostnamectl
  Operating System: Raspbian GNU/Linux 11 (bullseye)

$ unbound -V
Version 1.13.1

$ dig google.com @127.0.0.1 -p 5335

; <<>> DiG 9.16.48-Raspbian <<>> google.com @127.0.0.1 -p 5335
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21242
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;google.com.                    IN      A

;; ANSWER SECTION:
google.com.             300     IN      A       172.217.168.206

;; Query time: 59 msec
;; SERVER: 127.0.0.1#5335(127.0.0.1)
;; WHEN: Sun Jun 01 22:36:56 CEST 2025
;; MSG SIZE  rcvd: 55

VM running v6:

$ hostnamectl
Operating System: Debian GNU/Linux 12 (bookworm)

$ sudo unbound -V
Version 1.17.1

$ dig google.com @127.0.0.1 -p 5335

; <<>> DiG 9.18.28-1~deb12u2-Debian <<>> google.com @127.0.0.1 -p 5335
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 5423
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;google.com.                    IN      A

;; ANSWER SECTION:
google.com.             300     IN      A       172.217.168.206

;; Query time: 48 msec
;; SERVER: 127.0.0.1#5335(127.0.0.1) (UDP)
;; WHEN: Sun Jun 01 22:37:40 CEST 2025
;; MSG SIZE  rcvd: 55

[Falconcrest]

Thank you. In the meantime I have read in another forum that some servers no longer deliver this flag....

I have been using

dig dnssec.works @127.0.0.1 -p 5335

for a long time, so there is currently no ad-flag anymore.

But another user wrote that it works with

dig sigok.ippacket.stream @127.0.0.1 -p 5335

So it is probably not a problem with unbound.