"Resolving Host" is making the new Microsoft Edge unusable.

Using Windows 10, go to settings, then system, then open computer proxy settings, turn off "automatically detect settings". It solved my issue.

Security software has been sometimes observed to cause problems of this nature.

Visiting edge://histograms/Net.DNS will show the histograms of DNS lookup times which will help confirm that this is really an issue with slow DNS vs. any sort of UX glitch.

Chromium has two major codepaths for DNS resolution: One relies upon the system resolver, and one relies upon resolution logic within Chromium itself. For compat reasons, on Windows, Chromium historically used the system resolver rather than its own built in DNS resolver client. They had found (many years ago) that some home routers behaved poorly when the Chromium resolver performed many resolutions in parallel, and sometimes poor performance was observed if routers or upstream DNS did not perform well with IPv6 queries.

Over the last decade, Chromium has started switching on their own internal resolver more broadly, in part because the built-in resolver has support for DNS-over-HTTPS, a new feature that obtains DNS information in a fundamentally different way (improving security and privacy). If you’re seeing good DNS performance from other browsers (which typically only use the system resolver) but poor performance from Chromium, the built-in client may be the culprit.

If you’re encountering this problem on Windows, collecting a NetLog (https://textslashplain.com/2020/01/17/capture-network-logs-from-edge-and-chrome/) will allow us to analyze it (https://textslashplain.com/2020/04/08/analyzing-network-traffic-logs-netlog-json/) to take a closer look at what’s happening under the hood. Ultimately if the problem does appear to be that the DNS request itself is simply slow, we may need a lower-level (e.g. Wireshark PCAP) network trace to get a complete picture of what’s going on.

If you're running the very latest version of Edge 86+ on Windows on a non-Enterprise device, you might try enabling DNS-over-HTTPS (see edge://settings/?search=secure%20dns) to see if it solves the problem. 

We have a group policy that disables the built-in DNS client: https://docs.microsoft.com/en-us/deployedge/microsoft-edge-policies#builtindnsclientenabled;

Yeah, that's probably it. Also, though Trump is gathering the data, it's Obama's fault. :)

Are all your accounts, (i.e.  cell phone, p.c., Ipad, Ipod, Apple, signed in to the same Microsoft account? 

I had a similar problem . Then I just assigned the same User ID and password to all