Not working with Spotify

[ghost]

This is a great AdBlock but I can't figure out how to make it work with Spotify. With every other app or browser it works great.

I do not use the custom DNS servers, only the domain filters.

As side note, netguard works fine with Spotify and I use Steven black hosts on both apps.

Does dns66 use a different method of blocking ads?

Thank you :)

[julian-klode]

Can you please clarify what do you mean with "Not working with Spotify #55"? Does spotify stop working for you, do you have ads in spotify, etc?

And yes, they are slightly different I think. Netguard redirects all traffic, DNS66 only traffic to DNS servers (and drops non DNS traffic to those right now).

[ghost]

Sorry I wasn't clear.
I mean that it does not block ads from Spotify. But it's still active and blocking ads from chrome and other apps..
Every few songs I still get Spotify ads.

[julian-klode]

Ah OK. I can't really help there, as I'm paying for Spotify Premium. You might want to check if those hosts are really blocked (try a ping app or dns lookup app or something).

0.0.0.0 gads.pubmatic.com
0.0.0.0 spclient.wg.spotify.com

I'll check what the parser says about the file and if it adds them to the final blacklist.

That said, I really like the people at Spotify, and their ads are not really what I'm personally interested in blocking (I mostly wrote the app to have these awful popup banners and stuff blocked ...).

[ghost]

Sure, I wasn't demanding or anything.
Just genuine curious as why it didn't block. Might be a bug on the parser and maybe not only these address could be leaking.

I manually put these address on the block list and all seems gold :).

Awesome work.

[julian-klode]

Hmm I just checked the parser and it correctly read these hosts from the file.

[smichel17]

edit 2017-08-12: I discovered that this comment is linked in relation to blocking spotify ads on the web player. For me, the rules below no longer work for the web player (they still work in DNS66); I found a fix here, which you should also get if you update your lists.

---

This is not a bug in DNS66.

It happens because spotify changed where they serve ads from, and the new servers, for whatever reason, have not made it into hosts file lists that I've found.

I put up a txt file on my own website that contains the block below. When I add the link to DNS66, it successfully block ads in spotify (not linking to it because I don't want people to start using it and be upset if I move it or something).

127.0.0.1 audio2.spotify.com
127.0.0.1 crashdump.spotify.com
127.0.0.1 adeventtracker.spotify.com
127.0.0.1 log.spotify.com
127.0.0.1 analytics.spotify.com
127.0.0.1 ads-fa.spotify.com
127.0.0.1 audio-ec.spotify.com
127.0.0.1 heads-ec.spotify.com
127.0.0.1 prod.spotify.map.fastlylb.net
127.0.0.1 sto3.spotify.com
127.0.0.1 spclient.wg.spotify.com
127.0.0.1 upgrade.spotify.com

I'm pretty sure those entries are not all necessary, but it works without breaking anything that I can tell, so I haven't had to figure out which are the important ones.

[smichel17]

@labors89 Made a gist you can use: https://gist.githubusercontent.com/smichel17/2ad8c3f18df64eb1d5a4b01d70646058/raw/91412355ee401f5795d05fe6d9bf74da8200fecc/spotads.txt

@julian-klode I think this can be closed.

[smed79]

Just FYI, for desktop web browser in Adblock Plus, AdBlock, µBo or Adguard add this filter :

/mp3-ad/*$domain=open.spotify.com
or
||cloudfront.net/mp3-ad/

[MrOats]

Just experienced this issue only because of issue #66, else works fine over Wi-Fi using DNS66.

Note: I am using fast.t-mobile.com and ipv6 as well, will force it to use IPv4 to see how it goes.

[MrOats]

Well after fixing adjusting my Mobile Data Network to use IPv4 only, it has been blocking ads from Spotify (and other places too) just fine.

Can confirm now that blocking Spotify ads is fully functional through DNS66.

[julian-klode]

OK, that should be fixed with the IPv6 support in master, see #4 and #68. There will be a release in the next days, so you can verify it yourself :)