[Android Software/Hacking General [Developers Only]] Timmmmaaahh!:
Since this is about DNS blocking, IP's aren't really involved.

Are you sure you searched the whole document, [MENTION=8500328]jaymoker[/MENTION]? I count 27 hits when searching for Spotify:

List A

0.0.0.0 adeventtracker.spotify.com

0.0.0.0 ads-fa.spotify.com

0.0.0.0 analytics.spotify.com

0.0.0.0 audio2.spotify.com

0.0.0.0 audio-ec.spotify.com

0.0.0.0 audio-sp-sto.spotify.com

0.0.0.0 crashdump.spotify.com

0.0.0.0 desktop.spotify.com

0.0.0.0 embed.spotify.com

0.0.0.0 **edit**

0.0.0.0 **edit**

0.0.0.0 **edit**

0.0.0.0 gew1.ap.spotify.com

0.0.0.0 heads-ec.spotify.com

0.0.0.0 log.spotify.com

0.0.0.0 lon6-accesspoint-a33.lon6.spotify.com

0.0.0.0 prod.spotify.map.fastlylb.net

0.0.0.0 spclient.wg.spotify.com

0.0.0.0 **edit**

0.0.0.0 **edit**

0.0.0.0 **edit**

0.0.0.0 **edit**

0.0.0.0 **edit**

Note: I've edited out the malicious ones as they serve no purpose in this context.

My DNS testing on a non-adblocking system with AdAway revealed the following:

List B

ad.doubleclick.net

adeventtracker.spotify.com *

api.segment.io *

audio-fa.spotify.com

audio-sp-bma.spotify.com

ff.video-ak.cdn.spotify.com

heads-ak.spotify.com.edgesuite.net

i.scdn.co

profile-images.scdn.co

pubads.g.doubeclick.net

quicksilver.scdn.co

securepubads.g.doubleclick.net *

spritemaps.cdn.spotify.com

upsell.scdn.co

z.moatads.com *

* = also found in MoaAB

With some Ducking, I found another list on the net that is designed specifically for adblocking in Spotify:

List C

0.0.0.0 adclick.g.doublecklick.net

0.0.0.0 adeventtracker.spotify.com

0.0.0.0 ads-fa.spotify.com

0.0.0.0 analytics.spotify.com

0.0.0.0 audio2.spotify.com

0.0.0.0 b.scorecardresearch.com

0.0.0.0 bounceexchange.com

0.0.0.0 bs.serving-sys.com

0.0.0.0 content.bitsontherun.com

0.0.0.0 core.insightexpressai.com

0.0.0.0 crashdump.spotify.com

0.0.0.0 d2gi7ultltnc2u.cloudfront.net

0.0.0.0 d3rt1990lpmkn.cloudfront.net

0.0.0.0 desktop.spotify.com

0.0.0.0 doubleclick.net

0.0.0.0 ds.serving-sys.com

0.0.0.0 googleadservices.com

0.0.0.0 googleads.g.doubleclick.net

0.0.0.0 gtssl2-ocsp.geotrust.com

0.0.0.0 js.moatads.com

0.0.0.0 log.spotify.com

0.0.0.0 media-match.com

0.0.0.0 omaze.com

0.0.0.0 open.spotify.com

0.0.0.0 pagead46.l.doubleclick.net

0.0.0.0 pagead2.googlesyndication.com

0.0.0.0 partner.googleadservices.com

0.0.0.0 pubads.g.doubleclick.net

0.0.0.0 redirector.gvt1.com

0.0.0.0 s0.2mdn.net

0.0.0.0 securepubads.g.doubleclick.net

0.0.0.0 spclient.wg.spotify.com

0.0.0.0 tpc.googlesyndication.com

0.0.0.0 v.jwpcdn.com

0.0.0.0 video-ad-stats.googlesyndication.com

0.0.0.0 weblb-wg.gslb.spotify.com

0.0.0.0 www.googleadservices.com

0.0.0.0 www.googletagservices.com

0.0.0.0 www.omaze.com

List B & C reveal two overlaps: "z.moatads.com" & "api.segment.io". I've done some more Ducking and moatads seems to be an advertisement company and I think segment is used for tracking their users so that seems to be a dead end.

Comparing List A to List C, these seem interesting candidates though:

0.0.0.0 audio-ec.spotify.com

0.0.0.0 audio-sp-sto.spotify.com

0.0.0.0 embed.spotify.com

0.0.0.0 gew1.ap.spotify.com

0.0.0.0 heads-ec.spotify.com

0.0.0.0 lon6-accesspoint-a33.lon6.spotify.com

I can't test this right now so can one of you try removing (some of) these findings and report back?