I am using SONOS, with a music library on a Synology NAS. With the last update of the Sonos App the Sonos App on Android didn't show that music library any more. On Apple and Windows they still show.
Sonos analysed the situation through their diagnosis-report and saw a lot of errors on the network and that I was using a local DNS. They adviced to disable that and see what happend.
And indeed, after disabling Pi_hole (on a raspberry-pi) my Android apps showed the Music Library again. I don't understand this, since the music library is configured on a local IP-address.
Can anybody give possible explanation how pi-hole could frustrate my Sonos / NAS setup and more important, how to solve this with re-enabling the pi-hole?
It might be that the Sonos app tries to connect to a domain that is on the Pi-hole blacklist.
Tail the Pi-hole logs when opening the Sonos app or when querying the music library on NAS to see if any get redirected to the Pi-hole IP:
Did you ever figure this out? I just installed pi-hole (running in docker on a mac mini on my network). It seemed to be working perfectly, except that I can't stream local libraries on sonos anymore. I tailed the log and looked at any sonos-related domains and didn't see any obvious blacklisting. I assume it has to do with lookup of local domains (in my case: Media-Server or Media-Server.localdomain) but I couldn't figure it out.
Answered my own question, in case anyone finds this: Under DNS, Advanced DNS Settings, you need to uncheck "Never forward non-FQDNs" and "Never forward reverse lookups for private IP ranges."