I have been meeting strange DNS problems in Fedora 33 that I did not meet in Fedora 32. I spent some time trying to debug them and then thought of asking for help. This is the behavor I see:
Out of the box, WiFi gets assigned a DNS server automatically, but on my laptop no browser can resolve any DNS query
If I manually switch on Fedora the WiFi connection to use 18.104.22.168 as a DNS server instead of the automatically assigned one, Firefox can solve DNS calls and works fine, while any Chrome-based browser (Chrome, Chromium, Vivaldi) hangs like it cannot solve the DNS query
Setting the router to use 22.214.171.124 as a DNS does not solve the problem
All this is without VPN. Other users have reported here problems when connected to VPN, but for me it happens with a normal connection. I tried to switch to use the hotspot functionality from my phone (bypassing the router, to check if the problem could be with the router) but the problem persists.
Some people think that DNS problems could be caused by the move to systemd-resolved and advise to disable it, but I’d rather keep it on and try to debug the problem: I can use Firefox just fine.
Could we please try to debug the problem together? Let me know if you need more information about the system!
I have a similar problem too. I have 2 fedora systems and i only use firefox. Laptop when connected with wifi has no problem even with VPN enabled but when i switch to ethernet, problem appears. Desktop connected with cable has the same issue. I tried some suggestions such as disabling local dns, disabling VPN, using 126.96.36.199 dns, but problem remains. This issue happened lately after applying updates ( i think).
Link 2 (wlp58s0): 188.8.131.52
Link 3 (virbr0):
Link 4 (virbr0-nic):
Link 2 (wlp58s0): ~.
Link 3 (virbr0):
Link 4 (virbr0-nic):
hosts: files mdns4_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] myhostname dns
options edns0 trust-ad
Do you see anything strange? Regarding turning on the DNS encryption, the directory
/etc/systemd/resolved.conf.d/ does not exist in my Fedora 33 installation.
Here is the results, with the first lines obscured to hide my location for privacy. Currently every time I suspend or reboot, Chrome’s working status can change. It’s weird. Maybe you are right and it’s not a DNS problem at all, and it’s a generic network problem. But I did not have it with Fedora 32. Anyway, here is the result:
Dear @vgaetera, the flag is not present for me and the settings say that chrome is managed by an organization. If you google online, you will find that Chrome figured out that the DNS server is not compatile with DNS over https, and turned it off. Thank you again for helping me with this
If possible, check whether the problem persists in Chromium installed from the main Fedora repository or Chromium Freeworld from RPM Fusion.
Try to reproduce the issue under a new user with default profile.
Problem fixed for me. I tried some suggestions but i reverted all to initial settings (local dns, auto dns) and now everything works as expected. I tried chrome and epiphany and everything worked ok but firefox remained sluggish. I changed firefox setting to no proxy (was system-proxy) and from now firefox works like other browsers. Even VPN is ok. Still don’t know what was the problem.
@charnik I tried the same, no luck. @vgaetera Yes, it happens also with Chromium installed from the Fedora repos:
Name : <font color="#2AA1B3">chromium</font>
Version : 87.0.4280.66
Release : 1.fc33
Architecture : x86_64
Size : 317 M
Source : chromium-87.0.4280.66-1.fc33.src.rpm
Repository : @System
From repo : updates
Summary : A WebKit (Blink) powered web browser
URL : http://www.chromium.org/Home
License : BSD and LGPLv2+ and ASL 2.0 and IJG and MIT and GPLv2+ and ISC and OpenSSL and (MPLv1.1 or GPLv2 or LGPLv2)