Now that you mention it, it does appear to do so. The output is:
Wireless LAN adapter Wi-Fi:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Dual Band Wireless-N 7260
Physical Address. . . . . . . . . : ##-##-##-##-##-## (annonymized)
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::c492:9df4:c9e4:6075%18(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.12(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 15. september 2019 02:46:08
Lease Expires . . . . . . . . . . : 15. september 2019 02:52:08
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . : 142640882
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-23-F0-E8-F7-10-C3-7B-1B-F3-48
DNS Servers . . . . . . . . . . . : 192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled
At 192.168.0.1 is my router. I fail to see why my PC doesn't go for 192.168.0.24 given that the output of pihole status is:
[✓] DNS service is running
[✓] Pi-hole blocking is Enabled
I have before your latest reply restarted both the router and the pihole. The same issue is observed when I attempt to access pi.hole/admin from my phone, too.