dnshome-networking
I don't understand why imgur.com is not resolving on my computer. I have tried Google DNS and it still doesn't work. Neither does the DNS from my broadband provider. However, if I connect over a VPN it works. Why is this? Also, my phone has the same issue using WiFi, so it is definitely tied to my home network. How can I diagnose and fix this issue?
Edit: pics of imgur.com in browser with and without vpn. Posted via VPN.
I had the same issue, frustrating to get no connection when connecting to the windows hostednetwork because of no DNS being sent to the connected devices.
I found the solution here: https://4sysops.com/archives/how-to-share-wi-fi-in-windows-8-with-internet-connection-sharing-ics/ I read it before but didn't get it until the second time around, the steps that go like this are important:
Control Panel\Network and Internet\Network Connections and you will see your internet connection and your hostednetwork as something like "Local Area Connection* XX". Even though it's a wifi connection you are hosting, it will still be called a "LAN" connection.Now in summary, when you connect to the hotspot after sharing the source connection with your hostednetwork connection, the DNS will start being sent to the devices that are connected via DHCP automatically.
Addendum A: Make sure that there is no DNS setting manually set on the "Local Area Connection*3" for example, it should just be empty: 
Checked the DNSSEC settings between Google and Cloudflare are consistent
They are not. The delegation you submitted through Google specified an RSA key (algorithm 5), but the actual zone at Cloudflare is using an ECDSA P-256 key (algorithm 13).
You can see the DNSSEC validation status at DNSViz: original scan, latest scan.
Algorithm mismatch makes signatures impossible to verify, so people using validating resolvers will get a SERVFAIL error while non-validating resolvers have no issues with the domain. The Google public resolver (8.8.8.8) is a validating one.
To fix this, change the DNSSEC settings at Google to specify ECDSA P-256 (13) as the algorithm. You may need to wait up to 24 hours for the old DS records to expire from caches. (DNSViz will bypass caching and will see the changes sooner, but you have to click "Update now" to refresh the diagram.)
1 (The shown key size of 512 bits is normal for an EC P-256 key.)
Best Answer
Your router has DNS caching issues. I had an older Linksys E1000 Wireless-N router, but I've found the issue also exists with other (cheaper) models.
Easiest thing is resetting your router, which usually cleans out the DNS cache. Check that your firmware is up-to-date, and update it if it's not. Another option is getting another router.