Got a new windows 10 computer recently & could not get it to allow me to use my microsoft account to log in, until I went into the TCP/IPv4 properties & set a specific, non-pihole DNS server--like so:
From some sleuthing I believe I traced the issue to the domain logincdn.msauth.net being unreachable. But when I looked for it or related domains in my query log in the admin console, I found nothing. When I disabled the pihole entirely through the admin console, there was no difference--host not found. So I added a regex entry to the whitelist like so: (\.|^)msauth\.net$ and still I can't resolve that domain (by which I mean ping comes back with "Ping request could not find host logincdn.msauth.net.")
If I change to DNS server 8.8.8.8 then I can immediately ping that domain, and pull up a default page in a browser.
Expected Behaviour:
Domain should show in the query log
Disabling the pihole should allow every valid domain to resolve, including logincdn.msauth.net
Whitelisting anything ending in msauth.net should allow the domain to resolve.
Actual Behaviour:
Domain remains blocked so long as I am using the pihole as my DNS server.
I don't think it's on any of my lists--doing a partial match search for 'logincdn' gets me [i] No results found for logincdn within the block lists.
Agree that it's not the loveliest thing, but give that it's invoked by e.g., login.live.com, and its reachability is also completely correlated to being able to establish a new microsoft account login on my computer, I'd like to figure out how that domain is getting blocked.
Then it's not Pi-hole that is causing the issues. There is no listing of anything that would be blocking the domain to start with. The whitelist entry isn't doing anything.
