I posted a similar problem the other day, and the response was to direct me to this thread.
First let's start with some of the text of what I posted:
Expected Behaviour:
That Pi-hole would provide DNS services to my computer from work.
This is on a Windows 11 computer which is from my work and is configured for Active Directory at that location.Actual Behaviour:
The computer is receiving an IP address, gateway address, netmask, and DNS address (the Pi-hole server). However, the computer can't reach Internet services as name resolution is not happening. I can verify all the addresses are present, but at the command line I try a simple ping of "www.google.com" and I get the "Ping request could not find host www.google.com." Then I go to the network settings and change the DNS type to manual and enter 1.1.1.1, go back to the command line window, and repeat the ping attempt. This time it resolves Google instantly and pings happen as expected. Obviously Pi-hole doesn't like to play with my work computer.
While there's talk in this thread of this being a Microsoft problem, I dispute that. Prior to using Pi-hole (about a week ago), all DNS here was handled by our home router. Windows never had a problem with my work computer (which is configured for an Active Directory domain).
With so many people who are working from home now, we'd have to expect them to bring home their work computers. In my office alone, we had hundreds of people going home with their work computers. They all worked fine on their networks... expect now for me (because I'm the only one using Pi-hole).
Was this actually not a problem prior to some update to Pi-hole in December? Is the only way for Pi-hole users to "fix" this to do some manual config file hacking for every computer that they might use that has its own configured domain? How is lack of DNS services to a validated DHCP client not being caused by Pi-hole?