Website won't resolve with PiHole DNS, does with manual DNS on PCs

[offbeatdave]

Expected Behaviour:

Website https://www.showmyhomework.co.uk/login should display when using PCs through Pi-hole DNS servers

Actual Behaviour:

Website https://www.showmyhomework.co.uk/login won't display (blank screen) when using Win 7 and Win 10 PCs via Pi-hole (any DNS servers selected). When DNS servers (e.g. Google, Cloud9) are set manually in Win 10 or Win 7, therefore bypassing Pi-hole DNS, the site displays correctly.
PC setup when going through Pi-hole is:
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.2 (Pi-hole)
DNS Servers . . . . . . . . . . . : 192.168.0.2 (Pi-hole)

Debug Token:

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

[DanSchaper]

It looks like your /etc/pihole/setupVars.conf is not set correctly for your IP addressing. Have you manually edited the file or changed any IP address lists? Try running pihole -r and reconfigure the Pi-hole with the correct IP addresses.

[offbeatdave]

I have run the pihole -r and setupVars.conf is as follows:

BLOCKING_ENABLED=true
DHCP_ACTIVE=true
DHCP_START=192.168.0.3
DHCP_END=192.168.0.251
DHCP_ROUTER=192.168.0.1
DHCP_LEASETIME=24
PIHOLE_DOMAIN=Pi-hole
DHCP_IPv6=true
DHCP_rapid_commit=false
PIHOLE_INTERFACE=eth0
IPV4_ADDRESS=192.168.0.2/24
IPV6_ADDRESS=fdaa:bbcc:ddee:0:2ee:9ff:fec9:9226
QUERY_LOGGING=true
INSTALL_WEB_SERVER=true
INSTALL_WEB_INTERFACE=true
LIGHTTPD_ENABLED=true
DNSMASQ_LISTENING=single
PIHOLE_DNS_1=8.8.4.4
PIHOLE_DNS_2=2001:4860:4860:0:0:0:0:8844
PIHOLE_DNS_3=9.9.9.9
PIHOLE_DNS_4=2620:fe::fe
DNS_FQDN_REQUIRED=false
DNS_BOGUS_PRIV=false
DNSSEC=false
CONDITIONAL_FORWARDING=false

However, the site in question still doesn't work unless I set the DNS servers in Windows.

[offbeatdave]

Solved! I've just found that disabling PiHole via the disable menu option in the web interface allows the site to load. Another look at the query log showed that although showmyhomework.co.uk was whitelisted, the login page also accesses d2wy8f7a9ursnm.cloudfront.net, which was being blocked. Allowing it allowed the site to load up as expected.