Some DNS queries not working since upgrade to v5

[Taomyn]

Expected Behaviour:

nslookup slscr.update.microsoft.com

Server:         192.168.1.1
Address:        192.168.1.1#53

Non-authoritative answer:
slscr.update.microsoft.com      canonical name = slscr.update.microsoft.com.akadns.net.
slscr.update.microsoft.com.akadns.net   canonical name = sls.update.microsoft.com.akadns.net.
sls.update.microsoft.com.akadns.net     canonical name = sls.emea.update.microsoft.com.akadns.net.
Name:   sls.emea.update.microsoft.com.akadns.net
Address: 13.74.179.117
Name:   sls.emea.update.microsoft.com.akadns.net
Address: 2a01:111:f335:1792::f001:7a5

Actual Behaviour:

nslookup slscr.update.microsoft.com 192.168.1.9
Server:         192.168.1.9
Address:        192.168.1.9#53

Non-authoritative answer:
*** Can't find slscr.update.microsoft.com: No answer

Both commands performed on the Pi itself, and 192.168.1.1 is the DNS server on my firewall that Pi-hole also forwards to

This is logged in the Pi-hole console

May 11 12:02:48 dnsmasq[1067]: query[A] slscr.update.microsoft.com from 192.168.1.9
May 11 12:02:48 dnsmasq[1067]: forwarded slscr.update.microsoft.com to 192.168.1.1
May 11 12:02:48 dnsmasq[1067]: reply slscr.update.microsoft.com is <CNAME>
May 11 12:02:48 dnsmasq[1067]: reply slscr.update.microsoft.com.akadns.net is <CNAME>
May 11 12:02:48 dnsmasq[1067]: query[AAAA] slscr.update.microsoft.com from 192.168.1.9
May 11 12:02:48 dnsmasq[1067]: forwarded slscr.update.microsoft.com to 192.168.1.1
May 11 12:02:48 dnsmasq[1067]: reply slscr.update.microsoft.com is <CNAME>
May 11 12:02:48 dnsmasq[1067]: reply slscr.update.microsoft.com.akadns.net is <CNAME>

Debug Token:

https://tricorder.pi-hole.net/rgpjzu4cfi

[Taomyn]

I wanted to add that whitelisting *.update.microsoft.com.akadns.net allows it to work but the query log makes mention of it being blocked by something in my lists.

I'm going to find out how to reset the lists to the defaults that come with v5 but it would be helpful to know which of mine is the culprit so I can fix just that.

[Taomyn]

Apologies, seems I needed to refresh the browser with Ctrl-Shift-R, so I now I see why

Maybe this post will help others coming across the same issue.