The Spotify client has been sending extra Valid DNS requests to spclient.wg.spotify.com but its triggered on the back of many other microsoft DNS requests. Hence the hosts file.
I found a handy DNS program which I have been using to troubleshooting the windows > pihole setup.
I had wireshark running as well and got a diagraph of what goes on with spotify.
I have a 4 GB packet log over 2 days with ads on spotify. My PC is too old to do much with it.
I had bat file with 6 Nslookup's running in an endless loop to test the speed of DNS in windows and check for timeouts.
With the help of Dnssniffer I was able to see the requests, some go unanswered. You could also see the triggered requests.
I ended up adding each domain as it came along.
Here's addition to the hosts file used on all my Piholes, Windows, Linux.
# dnsquerysniffer
127.0.0.1 13.224.186.35.in-addr.arpa
127.0.0.1 lh3.googleusercontent.com
127.0.0.1 dns.msftncsi.com
127.0.0.1 login.live.com
127.0.0.1 optimizationguide-pa.googleapis.com
127.0.0.1 www.msftconnecttest.com
127.0.0.1 go.microsoft.com
# tabs after microsoft.com
127.0.0.1 go.microsoft.com
127.0.0.1 go.microsoft.com
127.0.0.1 go.microsoft.com
127.0.0.1 v10.events.data.microsoft.com
127.0.0.1 umwatson.events.data.microsoft.com
127.0.0.1 slscr.update.microsoft.com
127.0.0.1 teams.events.data.microsoft.com
127.0.0.1 checkappexec.microsoft.com
127.0.0.1 heads-fa.scdn.co
127.0.0.1 i.scdn.co
127.0.0.1 heads-fa.scdn.co
127.0.0.1 www.googletagservices.com
127.0.0.1 checkappexec.microsoft.com
127.0.0.1 dealer.spotify.com
# Tabs
127.0.0.1 dealer.spotify.com
127.0.0.1 dealer.spotify.com
127.0.0.1 dealer.spotify.com
127.0.0.1 pagead2.googlesyndication.com
127.0.0.1 pubads.g.doubleclick.net
127.0.0.1 securepubads.g.doubleclick.net
127.0.0.1 adeventtracker.spotify.com
127.0.0.1 pubads.g.doubleclick.net
127.0.0.1 ads-eu.amillionads.com
127.0.0.1 googleads.g.doubleclick.net
127.0.0.1 insight.adsrvr.org
127.0.0.1 media-eu.amillionads.com
127.0.0.1 gcdn.2mdn.net
127.0.0.1 adeventtracker.spotify.com
127.0.0.1 evoke-windowsservices-tas.msedge.net
127.0.0.1 assets.msn.com
127.0.0.1 settings-win.data.microsoft.com
# sp-gue1 replys 127.0.0.1 before this.
127.0.0.1 ap-gue1.spotify.com
127.0.0.1 api-partner.spotify.com
127.0.0.1 ade.googlesyndication.com
127.0.0.1 video-fa.scdn.co
127.0.0.1 update.ultraviewer.net
127.0.0.1 vortex.data.microsoft.com
127.0.0.1 dc.services.visualstudio.com
127.0.0.1 bloodhound.spotify.com
127.0.0.1 dc.services.visualstudio.com
127.0.0.1 config.teams.microsoft.com
# 127.0.0.1 5.1.168.192.in-addr.arpa
127.0.0.1 b.f.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.f.f.ip6.arpa
127.0.0.1 3.0.0.0.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.f.f.ip6.arpa
127.0.0.1 b.f.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.f.f.ip6.arpa
127.0.0.1 3.0.0.0.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.f.f.ip6.arpa
127.0.0.1 b.f.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.f.f.ip6.arpa
127.0.0.1 3.0.0.0.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.f.f.ip6.arpa
127.0.0.1 b.f.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.f.f.ip6.arpa
127.0.0.1 3.0.0.0.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.f.f.ip6.arpa
127.0.0.1 248.46.232.199.in-addr.arpa
127.0.0.1 248.46.232.199.in-addr.arpa
127.0.0.1 248.46.232.199.in-addr.arpa
127.0.0.1 248.46.232.199.in-addr.arpa
127.0.0.1 arc.msn.com
This was the stats yesterday after My Nslookup loop running for a few hours.
It cycled approx 2000 times according to yahoo lookups and there was the spotify clent domain with 50000 hits.
I now have no adds on spotify in windows and linux. Have Android to test later.
Nslookup work better not so many timeouts.