dd-wrt DNSMasq list to block Windows 10 telemetry

Copy/paste into Additional DNSMasq Options under services, this will force the resolver to push 0.0.0.0 when any machine on the network wants to lookup one of the domain names involved. This has a benefit over firewalling it, as firewalling hostnames can fail if it uses roundrobin resolution and a previously unknown ip gets added to the RR, it's also much easier on the firewalls utilization. The list itself was aquired on another site, they seemed to throw in some ad domains (at the bottom), those may or may not have anything to do with the tracking.

I take no responsibility if any damage happens to your network connectivity and assumes the user knows how to enable dnsmasq properly on their firewall.

The list may or may not work in other non-dd-wrt firmware, this was made for: DD-WRT v3.0-r27745 std, so YMMV.

--- COPY what's below this ---

address=/vortex.data.microsoft.com/0.0.0.0
address=/vortex-win.data.microsoft.com/0.0.0.0
address=/telecommand.telemetry.microsoft.com/0.0.0.0
address=/telecommand.telemetry.microsoft.com.nsatc.net/0.0.0.0
address=/oca.telemetry.microsoft.com/0.0.0.0
address=/oca.telemetry.microsoft.com.nsatc.net/0.0.0.0
address=/sqm.telemetry.microsoft.com/0.0.0.0
address=/sqm.telemetry.microsoft.com.nsatc.net/0.0.0.0
address=/watson.telemetry.microsoft.com/0.0.0.0
address=/watson.telemetry.microsoft.com.nsatc.net/0.0.0.0
address=/redir.metaservices.microsoft.com/0.0.0.0
address=/choice.microsoft.com/0.0.0.0
address=/choice.microsoft.com.nsatc.net/0.0.0.0
address=/df.telemetry.microsoft.com/0.0.0.0
address=/reports.wes.df.telemetry.microsoft.com/0.0.0.0
address=/wes.df.telemetry.microsoft.com/0.0.0.0
address=/services.wes.df.telemetry.microsoft.com/0.0.0.0
address=/sqm.df.telemetry.microsoft.com/0.0.0.0
address=/telemetry.microsoft.com/0.0.0.0
address=/watson.ppe.telemetry.microsoft.com/0.0.0.0
address=/telemetry.appex.bing.net/0.0.0.0
address=/telemetry.urs.microsoft.com/0.0.0.0
address=/telemetry.appex.bing.net/0.0.0.0
address=/settings-sandbox.data.microsoft.com/0.0.0.0
address=/vortex-sandbox.data.microsoft.com/0.0.0.0
address=/survey.watson.microsoft.com/0.0.0.0
address=/watson.live.com/0.0.0.0
address=/watson.microsoft.com/0.0.0.0
address=/statsfe2.ws.microsoft.com/0.0.0.0
address=/corpext.msitadfs.glbdns2.microsoft.com/0.0.0.0
address=/compatexchange.cloudapp.net/0.0.0.0
address=/cs1.wpc.v0cdn.net/0.0.0.0
address=/a-0001.a-msedge.net/0.0.0.0
address=/statsfe2.update.microsoft.com.akadns.net/0.0.0.0
address=/sls.update.microsoft.com.akadns.net/0.0.0.0
address=/fe2.update.microsoft.com.akadns.net/0.0.0.0
address=/diagnostics.support.microsoft.com/0.0.0.0
address=/corp.sts.microsoft.com/0.0.0.0
address=/statsfe1.ws.microsoft.com/0.0.0.0
address=/pre.footprintpredict.com/0.0.0.0
address=/i1.services.social.microsoft.com/0.0.0.0
address=/i1.services.social.microsoft.com.nsatc.net/0.0.0.0
address=/feedback.windows.com/0.0.0.0
address=/feedback.microsoft-hohm.com/0.0.0.0
address=/feedback.search.microsoft.com/0.0.0.0
address=/rad.msn.com/0.0.0.0
address=/preview.msn.com/0.0.0.0
address=/services.social.microsoft.com/0.0.0.0
address=/lb.services.social.ms.akadns.net/0.0.0.0

# one or more of those below this line seems to interfere with android notifications, YMMV

address=/ad.doubleclick.net/0.0.0.0
address=/ads.msn.com/0.0.0.0
address=/ads1.msads.net/0.0.0.0
address=/ads1.msn.com/0.0.0.0
address=/a.ads1.msn.com/0.0.0.0
address=/a.ads2.msn.com/0.0.0.0
address=/adnexus.net/0.0.0.0
address=/adnxs.com/0.0.0.0
address=/az361816.vo.msecnd.net/0.0.0.0
address=/az512334.vo.msecnd.net/0.0.0.0