You are not logged in.
Brave and Google Chrome won't connect to internet and can't open any website. I don't have this problem with Firefox. I tried using new profiles also disabled firewall but it didn't help.
Last edited by niko787 (Yesterday 19:52:15)
Offline
ping -c1 google.com
ping -c1 8.8.8.8
resolvectl status
stat /etc/resolv.conf
cat /etc/resolv.confOffline
ping -c1 google.com
PING google.com (172.217.16.142) 56(84) bytes of data.
64 bytes from zrh04s06-in-f142.1e100.net (172.217.16.142): icmp_seq=1 ttl=117 time=24.6 ms
--- google.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 24.630/24.630/24.630/0.000 ms
ping -c1 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=116 time=26.3 ms
--- 8.8.8.8 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 26.309/26.309/26.309/0.000 ms
resolvectl status
Global
Protocols: +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: foreign
Current DNS Server: 1.1.1.1
DNS Servers: 1.1.1.1 1.0.0.1 2606:4700:4700::1111 2606:4700:4700::1001
Fallback DNS Servers: 9.9.9.9#dns.quad9.net 2620:fe::9#dns.quad9.net 1.1.1.1#cloudflare-dns.com 2606:4700:4700::1111#cloudflare-dns.com 8.8.8.8#dns.google
2001:4860:4860::8888#dns.google
Link 4 (wlo1)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
Default Route: no
Link 5 (virbr0)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
Default Route: no
Link 10 (enp0s29u1u2)
Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 mDNS/IPv4 mDNS/IPv6
Protocols: +DefaultRoute +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 1.1.1.1
DNS Servers: 1.1.1.1 1.0.0.1
Default Route: yes
Link 3 (enp0s25)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
Default Route: no
stat /etc/resolv.conf
File: /etc/resolv.conf
Size: 253 Blocks: 8 IO Block: 4096 regular file
Device: 253,0 Inode: 5768473 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2026-08-26 15:49:58.543685891 +0300
Modify: 2026-08-26 15:49:58.533380484 +0300
Change: 2026-08-26 15:49:58.540047274 +0300
Birth: 2026-08-26 15:49:58.533380484 +0300
cat /etc/resolv.conf
# Generated by NetworkManager
nameserver 1.1.1.1
nameserver 1.0.0.1
nameserver 2606:4700:4700::1111
# NOTE: the libc resolver may not support more than 3 nameservers.
# The nameservers listed below may not be recognized.
nameserver 2606:4700:4700::1001Offline
systemd-resolved is not properly integrated as a DNS management for NetworkManager.
Delete "/etc/resolv.conf".
Replace it with a link to systemd-resolved's stub file:
ln -sf /run/systemd/resolve/stub-resolv.conf /etc/resolv.confAdditionally you can reconfigure NetworkManager:
# /etc/NetworkManager/conf.d/dns.conf
[main]
dns=systemd-resolvedRestart NetworkManager.
Check the outputs from seth's commands again.
Last edited by -thc (Yesterday 16:59:23)
Offline
systemd-resolved service was disabled. I enabled it and rebooted and that fixed the problem.
Offline
\o/
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Ftr, resolvectl responding means that resolved was running; the foreign mode should™ work but the stub mode is recommended - though just from what you posted it doesn't make a hell lot of sense that chromium could not resolve DNS
¯\_(ツ)_/¯
Offline