I'm having a hard time understanding why anyone would block "support.microsoft.com" since it can cause problems with Windows update - a bit of anti-security in my world.
Secondly... if i add a domain to whitelist with the webinterface it wont work.. its listed in the interface not actually added to the white list.. using console works fine.
I can quite understand why one would block such a domain. I'd do it!
It always depends on your point of view, though. I never owned and/or used a Windows machine. And I'll likely never do this in the future. So, at least for me, blocking this domain is harmless and maybe even beneficial in terms of security/privacy (there shouldn't be any traffic in my network to this domain, anyhow) - there is certainly a reason why it is contained in a "NoTrack" blocklist.
No doubt that it may not a very good choice for the wide range of computer users that are using Pi-Hole.
I completely understand your standpoint - and if this was for myself i would to.
But, support.microsoft.com does actually contain alot of good info and for the general public its not optimal to block the entire thing.
On another note - blocking "no track" domains is one thing.. but that should to the widest extend be the actual tracking domain.. not nesc. all websites that use tracking systems.
eg. you dont ban all of CNN because they use google analytics... you ban google analytics.
It would be nice with an option in pihole to select what excatly you want to ban.
The NoTrack list is actually just a list used by the application NoTrack which we also use. support.microsoft.com seems to have been added at the request of a user of NoTrack, but remember that we don't control the ad lists. If you would like you can:
Whitelist support.microsoft.com
Disable NoTrack's adlist in /etc/pihole/adlists.list (remember to follow the directions in /etc/pihole/adlists.default first)
I had this same problem with support.microsoft.com and I found that whitelisting akamaitechnologies.com solved my problem. Whitelisting support.microsoft.com wasn't enough.
Note the in such a situation you can always go to the Query Log to investigate which domains have been blocked at the time you wanted to access this particular page. You can use the Whitelist buttons there to permit all those queries from one place, so you don't have to search around a lot.