Windows 11 blocks user from enforcing local DNS settings

In recent discussions regarding home network configurations, a user faced challenges while attempting to set up a Pi-hole DNS server on their home Local Area Network (LAN). The user indicated that despite successful installation and configuration of the Pi-hole, their Internet Service Provider's (ISP) router, specifically a Rogers router/modem, did not provide an option for manual DNS settings. This lack of manual configuration options led the user to try setting DNS manually on one of their home computers, inputting the local IP address of the Pi-hole. After making these changes, the user reported that they continued to have full internet access, even with the Pi-hole powered down. This raised questions about the effectiveness of their DNS settings and whether Windows 11 was imposing restrictions that prevented the local DNS server from being the sole resolver for internet requests. The user undertook several troubleshooting steps, such as rebooting their computer and flushing the DNS cache using ipconfig, but they were still unable to resolve the issue. Potential explanations for the continued internet access included an active IPv6 configuration, which could allow access to sites even when the primary IPv4 DNS server was unresponsive. Furthermore, there was speculation about a backup DNS server being utilized in the event that the configured server became unreachable. Ultimately, the user was left concerned about their ability to enforce the local DNS settings on their devices, citing fears that Windows 11 might impose limitations that complicate home network management.