Your debug log shows that Pi-hole is correctly answering those requests:
*** [ DIAGNOSING ]: Pi-hole log
-rw-r--r-- 1 pihole pihole 4.0M Feb 14 08:44 /var/log/pihole.log
-----head of pihole.log------
Feb 14 00:00:30 dnsmasq[3628]: query[PTR] 1.1.168.192.in-addr.arpa from 192.168.1.139
Feb 14 00:00:30 dnsmasq[3628]: /etc/pihole/custom.list 192.168.1.1 is kviknet.lan
Pi-hole does not and cannot control client-side (mis)behaviour.
It is just listening for DNS requests in order to answer them.
Your client decides on any DNS query it sends.
You'd have to address this on the offending client, i.e. your soundbar.
You'd have to consult your soundbar's documentation and support for any details on if and how you would be able to control that behaviour.