DNS fails every couple of seconds, pings go through with no interruptions

Hello garuda fans

For the last week, i’ve been experiencing an issue with my DNS, where it stops working for a second, works fine for another couple of seconds, then fails again, etc. I’ve managed to narrow down the issue to my system, as I booted another mokka install on the same PC and everything works fine there. It’s very noticable as sometimes I try to load a website and i have to spam refresh until it loads.

I noticed that if I spam-use traceroute, it sometimes throws a DNS error:

jeredek@GarudaPC in ~
 ❯ traceroute google.com
google.com: Temporary failure in name resolution
Cannot handle "host" cmdline arg `google.com' on position 1 (argc 1)

Sometimes, it stops in the middle of a traceroute like this:

jeredek@GarudaPC in ~
❯ traceroute google.com
traceroute to google.com (142.250.203.142), 30 hops max, 60 byte packets
1  _gateway (192.168.1.1)  0.675 ms  0.762 ms  0.874 ms
connect: Permission denied

Additionally, while this happens, all pings go out and return without fail or delay difference.

Here are the outputs of:

  • garuda-inxi
System:
  Kernel: 6.16.4-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=ef979d8e-b3d2-4d91-8f56-49e20dc4feb2 rw rootflags=subvol=@
    vt.default_red=30,243,166,249,137,245,148,186,88,243,166,249,137,245,148,166
    vt.default_grn=30,139,227,226,180,194,226,194,91,139,227,226,180,194,226,173
    vt.default_blu=46,168,161,175,250,231,213,222,112,168,161,175,250,231,213,200
    ipv6.disable=1 quiet resume=UUID=283d4faa-020b-48a5-882d-7e5f968832d1
    loglevel=3
  Desktop: KDE Plasma v: 6.4.4 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
    Distro: Garuda base: Arch Linux
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: N/A
  Mobo: ASUSTeK model: ROG STRIX B360-F GAMING v: Rev 1.xx serial: <filter>
    part-nu: ASUS_MB_CNL uuid: c02ede6c-9fcb-ff68-49c5-0c9d920e84f2
    UEFI: American Megatrends v: 3101 date: 09/07/2021
CPU:
  Info: model: Intel Core i5-9600K socket: LGA1151 bits: 64 type: MCP
    arch: Coffee Lake gen: core 9 level: v3 note: check built: 2018
    process: Intel 14nm family: 6 model-id: 0x9E (158) stepping: 0xD (13)
    microcode: 0x104
  Topology: cpus: 1x dies: 1 clusters: 6 cores: 6 smt: <unsupported> cache:
    L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 1.5 MiB desc: 6x256 KiB
    L3: 9 MiB desc: 1x9 MiB
  Speed (MHz): avg: 4401 min/max: 800/4600 base/boost: 3663/8300 scaling:
    driver: intel_pstate governor: powersave volts: 1.1 V ext-clock: 100 MHz
    cores: 1: 4401 2: 4401 3: 4401 4: 4401 5: 4401 6: 4401 bogomips: 44398
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities: <filter>
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Navi 23 [Radeon RX 6600/6600
    XT/6600M] vendor: Micro-Star MSI driver: amdgpu v: kernel arch: RDNA-2
    code: Navi-2x process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4
    speed: 16 GT/s lanes: 16 ports: active: DP-1,HDMI-A-1
    empty: DP-2,DP-3,Writeback-1 bus-ID: 04:00.0 chip-ID: 1002:73ff
    class-ID: 0300
  Device-2: Creative Live! Cam Sync HD [VF0770]
    driver: snd-usb-audio,uvcvideo type: USB rev: 2.0 speed: 480 Mb/s lanes: 1
    mode: 2.0 bus-ID: 1-4:3 chip-ID: 041e:4095 class-ID: 0102 serial: <filter>
  Display: unspecified server: X.Org v: 24.1.8 with: Xwayland v: 24.1.8
    compositor: kwin_wayland driver: X: loaded: amdgpu
    unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
    gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 3200x1080 s-dpi: 96 s-size: 847x286mm (33.35x11.26")
    s-diag: 894mm (35.2")
  Monitor-1: DP-1 pos: primary,right model: Samsung C27R500 serial: <filter>
    built: 2019 res: mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 82 gamma: 1.2
    size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9 modes:
    max: 1920x1080 min: 720x400
  Monitor-2: HDMI-A-1 pos: left model: Samsung SyncMaster built: 2004 res:
    mode: 1280x1024 hz: 75 scale: 100% (1) dpi: 96 gamma: 1.2
    size: 338x270mm (13.31x10.63") diag: 433mm (17") ratio: 5:4 modes:
    max: 1024x768 min: 720x400
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast gbm: drv: radeonsi surfaceless: drv: radeonsi x11:
    drv: radeonsi inactive: wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.2.1-arch1.5
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 6600 XT (radeonsi
    navi23 LLVM 20.1.8 DRM 3.64 6.16.4-zen1-1-zen) device-ID: 1002:73ff
    memory: 7.81 GiB unified: no
  API: Vulkan v: 1.4.321 layers: 6 device: 0 type: discrete-gpu name: AMD
    Radeon RX 6600 XT (RADV NAVI23) driver: mesa radv v: 25.2.1-arch1.5
    device-ID: 1002:73ff surfaces: N/A device: 1 type: cpu name: llvmpipe
    (LLVM 20.1.8 256 bits) driver: mesa llvmpipe v: 25.2.1-arch1.5 (LLVM
    20.1.8) device-ID: 10005:0000 surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: corectrl, lact, radeontop
    wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel Cannon Lake PCH cAVS vendor: ASUSTeK driver: snd_hda_intel
    v: kernel alternate: snd_soc_avs,snd_sof_pci_intel_cnl bus-ID: 00:1f.3
    chip-ID: 8086:a348 class-ID: 0403
  Device-2: Advanced Micro Devices [AMD/ATI] Navi 21/23 HDMI/DP Audio
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 04:00.1 chip-ID: 1002:ab28 class-ID: 0403
  Device-3: JMTek LLC. Radon 610 driver: hid-generic,snd-usb-audio,usbhid
    type: USB rev: 1.1 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-11:6
    chip-ID: 0c76:1675 class-ID: 0300
  Device-4: Creative Live! Cam Sync HD [VF0770]
    driver: snd-usb-audio,uvcvideo type: USB rev: 2.0 speed: 480 Mb/s lanes: 1
    mode: 2.0 bus-ID: 1-4:3 chip-ID: 041e:4095 class-ID: 0102 serial: <filter>
  API: ALSA v: k6.16.4-zen1-1-zen status: kernel-api tools: N/A
  Server-1: PipeWire v: 1.4.7 status: n/a (root, process) with:
    1: pipewire-pulse status: active 2: wireplumber status: active
    3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: kernel
    port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15bc class-ID: 0200
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Info: services: NetworkManager, smbd, systemd-timesyncd, wpa_supplicant
Bluetooth:
  Device-1: ASUSTek Broadcom BCM20702A0 Bluetooth driver: btusb v: 0.8
    type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-5:4
    chip-ID: 0b05:17cb class-ID: fe01 serial: <filter>
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: N/A
Drives:
  Local Storage: total: 1.5 TiB used: 540.71 GiB (35.3%)
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Lexar model: SSD NM620 1TB
    size: 953.87 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: SN10660 temp: 31.9 C
    scheme: GPT
  SMART: yes health: PASSED on: 150d 7h cycles: 1,540
    read-units: 60,995,144 [31.2 TB] written-units: 23,809,282 [12.1 TB]
  ID-2: /dev/sda maj-min: 8:0 vendor: Kingston model: SH103S3120G
    family: Driven SSDs size: 111.79 GiB block-size: physical: 512 B
    logical: 512 B sata: 3.0 speed: 6.0 Gb/s tech: SSD serial: <filter>
    fw-rev: BBF0 temp: 29 C scheme: MBR
  SMART: yes state: enabled health: PASSED on: 2y 182d 6h cycles: 9034
    read: 60012 GiB written: 48618 GiB
  ID-3: /dev/sdb maj-min: 8:16 vendor: Western Digital
    model: WD5000AZLX-08K2TA0 family: Blue (CMR) size: 465.76 GiB block-size:
    physical: 4096 B logical: 512 B sata: 3.1 speed: 6.0 Gb/s tech: HDD
    rpm: 7200 serial: <filter> fw-rev: 1A01 temp: 35 C scheme: MBR
  SMART: yes state: enabled health: PASSED on: 5y 218d 13h cycles: 3024
Partition:
  ID-1: / raw-size: 919.19 GiB size: 919.19 GiB (100.00%)
    used: 342.39 GiB (37.2%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p2
    maj-min: 259:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 616 KiB (0.2%) fs: vfat block-size: 512 B dev: /dev/nvme0n1p1
    maj-min: 259:1
  ID-3: /home raw-size: 919.19 GiB size: 919.19 GiB (100.00%)
    used: 342.39 GiB (37.2%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p2
    maj-min: 259:2
  ID-4: /var/log raw-size: 919.19 GiB size: 919.19 GiB (100.00%)
    used: 342.39 GiB (37.2%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p2
    maj-min: 259:2
  ID-5: /var/tmp raw-size: 919.19 GiB size: 919.19 GiB (100.00%)
    used: 342.39 GiB (37.2%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p2
    maj-min: 259:2
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 31.25 GiB used: 0 KiB (0.0%) priority: 100
    comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 dev: /dev/zram0
  ID-2: swap-2 type: partition size: 34.38 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/nvme0n1p3 maj-min: 259:3
Sensors:
  System Temperatures: cpu: 39.0 C mobo: N/A gpu: amdgpu temp: 54.0 C
    mem: 50.0 C
  Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
Info:
  Memory: total: 32 GiB available: 31.25 GiB used: 4.24 GiB (13.6%)
  Processes: 337 Power: uptime: 13m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 12.47 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
    tool: systemctl
  Packages: pm: dpkg pkgs: 0 pm: pacman pkgs: 1774 libs: 457
    tools: octopi,paru pm: flatpak pkgs: 0 Compilers: clang: 20.1.8 gcc: 15.2.1
    Shell: Bash (sudo) v: 5.3.3 running-in: konsole inxi: 3.3.38
Garuda (2.8.2-2):
  System install date:     2025-07-17
  Last full system update: 2025-09-02
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut
  Windows dual boot:       No/Undetected
  Failed units:            
--- System Health Check Report ---
23/23 checks run in 0.76 seconds ⌛
Powered by garuda-health 🦅

✅ System health check passed. No issues found.

Additionally:

  • dmesg
  • journalctl
    (I had to paste them into pastebin as they are too large)

So far I’ve tried:

  • Updating the system
  • Changed my DNS settings to cloudflare and google
  • Checked if multiple networking services are running (They aren’t, just NetworkManager)
  • used IWD rather than wpa_supplicant
  • Re-mounting the e1000e driver
  • Disabled IPv6 (which my ISP doesn’t support)

Please, if you have any idea let me know, I’ve been at it for a week and I’m out of ideas.

EDIT:
I’ve also managed to notice that any traceroutes and tracepaths inside of my LAN network work fine, but as soon as i try to traceroute google.com or 1.1.1.1, it fails in the same way.

It also doesn’t matter if I use sudo or not.

I do not have a firewall enabled.

The current contents of my resolv.conf files are:

# Generated by NetworkManager
nameserver 8.8.8.8

The results of dig -x 8.8.8.8 @8.8.8.8 act the same way, it resolves fine but sometimes it fails.

Please post excerpts of your pacman log from immediately before/after the update that began to affect your dns queries.

Please state the date you believe the issue began.

This may be one of those rare instances where IPv6 must be enabled, and IPv4 disabled. I think there may be a regression relating to IPv4. Test that change out for any improvement.

Even if this doesn’t help with your DNS issue, there have been reports that using IPv6 has been a workaround to avoiding the DDoS issues plaguing Arch and the AUR recently.

There has been lengthy discussions on the Arch forum, and it has been mentioned that the linux-mainline kernel may help with this issue.

5 Likes

Looks like linux-mainline should but I haven’t tested rc4 yet Linux 6.14-rc4 [LWN.net]

If somehow linux-mainline doesn’t work to fix the issue, I’ve found that linux-tachyon works for me as its a kernel version a bit before these issues surfaced (and the bug even made it into the current LTS version).

(I’ve found https://speed.cloudflare.com/ quite handy to troubleshoot this as it measures packet loss in a way that it showed loss when the bug was accruing)

edit:
also worth noting that other systems that have Nvidia GPUs might want to try linux-tachyon first (with linux-tachyon-headers of course).

6 Likes

Mainline looks like a potential fix

3 Likes

I can in fact confirm that after switching from linux-zen to the linux-mainline kernel the issue has disappeared completely.

I went to Garuda Rani → System settings → Kernels and unselected zen, selected mainline, applied changes and restarted.

My DNS queries now complete without problems every single time. Thank you all for your support <3

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.