DNS_PROBE_STARTED only with Chrome not Firefox?
Solvedpatmoss Posted messages 2759 Status Membre -
Hello
Where might this come from and how can it be remedied?
Thank you
CPU: AMD Ryzen 5 5600G 3.9 GHz 6-Core,
MSI B550M PRO, G.Skil(2 x 8 GB) DDR4-3200, 500 GB M.2 NVMe Samsung 970 EVO Plus,
be quiet! Pure Base 500 ATX, SeaSonic FOCUS GX 650 W 80+ Gold-Windows 11 Home
3 réponses
Hello,
it's a typical message from Chrome (and its cousins Edge or Brave) when it loses connectivity with the configured DNS resolver.
Are you using the one provided by the router?
As long as it’s not permanent, it's not a big deal.
Firefox is more polite and will usually say something like this:
Hmm, we're having trouble finding that site. And there you go ....
But goodness, those line spaces are really annoying!!
I have NextDNS which filters, as a Custom DNS. Additionally, the Portmaster firewall filters, but with my personal DNS, so I don't see where it's blocking; let's say it works again, it crashes alternately under Chrome...
As I use both browsers.. when I say filter I may be expressing myself poorly, sorry...
CPU: AMD Ryzen 5 5600G 3.9 GHz 6-Core,
MSI B550M PRO, G.Skil(2 x 8 GB) DDR4-3200, 500 GB M.2 NVMe Samsung 970 EVO Plus,
be quiet! Pure Base 500 ATX, SeaSonic FOCUS GX 650 W 80+ Gold-Windows 11 Home