After upgrading to Fedora Linux 42 Workstation, I encountered a frustrating issue: although I could successfully connect to my Wi-Fi network, the internet wasn’t working. Local network resources were accessible, but DNS resolution failed—meaning no websites would load, and tools like ping
and dnf
couldn’t resolve hostnames.
The Symptom
- Wi-Fi connects successfully
- DNS resolution fails (resolvectl status showed no or incorrect DNS servers)
- LAN and local resources are accessible
- No internet connectivity
Hours of Troubleshooting Later...
I spent hours digging through logs, checking systemd-resolved, testing with different networks, and tweaking DNS settings. Eventually, I found a simple but effective fix that restored internet access immediately.
The Fix: Tweak IPv6 Settings in Network Manager
Here's what worked for me:
Open the Wi-Fi settings
- Click the network icon in the top-right corner
- Select your Wi-Fi network
- Click the gear ⚙️ icon to open Network Options
Go to the “IPv6” tab
-
Change the IPv6 method
- From: Automatic
- To: Automatic (DHCP only)
-
Reconnect to the Wi-Fi network
🔄 What Changed?
After making this change and reconnecting, I ran:
" resolvectl status"
Now, the DNS configuration was correct. Fedora properly picked up the DNS servers from the DHCP response, and internet connectivity was fully restored.
💡 Why This Happens
By default, Fedora 42 (like many modern Linux distributions) prefers IPv6 when it's available. However, if your network advertises an IPv6 route or DNS settings that are incomplete or misconfigured (which is surprisingly common), it can interfere with name resolution. Setting IPv6 to "Automatic (DHCP only)" prevents the system from using potentially broken SLAAC-based DNS settings.
0 Comments