Soundbar making tens of thousands of PTR requests

[Valiceemo]

Would anyone have any idea why a Philips soundbar is making this many PTR requests?
Literally none stop.
It's a Philips TAB8405/10, Play Fi enabled.
192.168.0.1 is my ISP provided router.
Pihole is my DHCP server, which is disabled on the router.

[jfb]

Are the PTR requests being answered with the name of the router? If not, the client may continually ask the same question in hopes of an answer.

From the Pi terminal, what is the output of the following command:

dig -x 192.168.0.1 @127.0.0.1

[Valiceemo]

Sorry, yes it's answered, I should have noted that.

pi@pihole:~ $ dig -x 192.168.0.1 @127.0.0.1

; <<>> DiG 9.11.5-P4-5.1+deb10u5-Raspbian <<>> -x 192.168.0.1 @127.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40744
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;1.0.168.192.in-addr.arpa.      IN      PTR

;; ANSWER SECTION:
1.0.168.192.in-addr.arpa. 2     IN      PTR     skyqhub.lan.

;; Query time: 4 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sun Oct 03 12:16:11 BST 2021
;; MSG SIZE  rcvd: 78

Edit
If I specify the port for dig, I see a different response....

pi@pihole:~ $ dig -x 192.168.0.1 @127.0.0.1 -p5335

; <<>> DiG 9.11.5-P4-5.1+deb10u5-Raspbian <<>> -x 192.168.0.1 @127.0.0.1 -p5335
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 56247
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1472
;; QUESTION SECTION:
;1.0.168.192.in-addr.arpa.      IN      PTR

;; AUTHORITY SECTION:
168.192.in-addr.arpa.   10800   IN      SOA     localhost. nobody.invalid. 1 3600 1200 604800 10800

;; Query time: 1 msec
;; SERVER: 127.0.0.1#5335(127.0.0.1)
;; WHEN: Sun Oct 03 12:18:38 BST 2021
;; MSG SIZE  rcvd: 112

[jfb]

@Valiceemo

If I specify the port for dig, I see a different response....
dig -x 192.168.0.1 @127.0.0.1 -p5335

This query is going directly to unbound and bypassing Pi-hole. Unbound does not know the name of your router.

[Valiceemo]

Ok, make sense.

Anything else I can do to diagnose?

[jfb]

I would check the forums for that soundbar.

[Valiceemo]

Yeah, I've had a look and can't really find anything useful.
Might just take it off the network. Shame though.