The Windows domain servers provide DNS resolution for local servers, but don't always provide accurate DNS resolution for remote servers. This means that, if I make a non-domain DNS server as my primary (such as Google's 8.8.8.8), I can resolve web servers but not local servers.
Fix your DNS problems | Computerworld DNS, though, can be your foe as well as your friend. DNS problems may stop you from being able to visit Web sites. If you're having problems connecting, it doesn't take much work to see if DNS is Fedora 31 can't resolve dns names anymore - on using Jul 02, 2020
This is happening because one of your packages uses JavaScript promises, which depend on the dns module, which is only available in Node.js (server-side) and not when your code runs in the browser. Though the implementation depends on it, it does not require it to work, so you can solve the problem by faking the existence of the dns module.
Aug 02, 2018 How to Clear the Google Chrome DNS cache on Windows Jul 11, 2017 [SOLVED] Unable to ping domain name but can ping IP - DNS
EDIT Just wanted to mention the output of systemd-resolve --status shows that the DNS Servers are the original ones configured by DHCP, and not the one overridden by the netplan configuration above. It doesn't seem to be accepting the netplan settings.
Pihole can't resolve any DNS requests : pihole