You are not logged in.
After running a system upgrade, DNS resolution in programs like ping and firefox would fail (although dig still worked). I had to downgrade libsystemd to libsystemd-233-7 in order to regain DNS functionality. Any idea what's up?
Last edited by dn3s (2017-07-12 06:38:37)
Offline
What have you tried in your troubleshooting to resolve this issue?
Matt
"It is very difficult to educate the educated."
Offline
I haven't had time to properly troubleshoot yet, so all I've done is temporarily revert:
pacman -U /var/cache/pacman/pkg/libsystemd-232-8-x86_64.pkg.tar.xz
I'm free later today to look into this more.
Offline
I had the same problem and i found it was a wrong configuration in /etc/nsswitch.conf
no idea why it was working before the update but not after it
Hope it helps
Offline
Same here:
My (working) nsswitch conf is:
# This file is part of systemd.
passwd: files
shadow: files
group: files
hosts: files mymachines resolve myhostname mdns_minimal
After upgrading, the config file remains the same, but dns resolution fails. Look forward to the experts figuring this one out!
[EDIT: worked around by adding 'dns' after hosts: files in nsswitch.conf.]
Last edited by sultanoswing (2017-07-08 22:45:44)
6.5.3.arch1-1(x86_64) w/Gnome 44.4
Arch on: ASUS Pro-PRIME x470, AMD 5800X3D, AMD 6800XT, 32GB, | Intel NUC 7i5RYK | ASUS ux303ua | Surface Laptop
Offline
appending "dns" to my /etc/nsswitch worked for me as well. although there has since been another libsystemd update that seems to have fixed this; the package-supplied nsswitch.conf now works. (if you have manually edited the file to workaround the issue, make sure to replace it with the .pacnew version created by the upgrade)
Offline
just wanted to add my DNS also broke when updating 5 packages, including systemd 233-6 to 233-7:
libsystemd
systemd
systemd-sysvcompat
bind-tools [9.11.1.P1-1 -> 9.11.1.P2-1]
libpng [unassuming update]
i fixed it by configuring resolvconf, but still no DNS in firejail
so after reading this topic i did
mv /etc/nsswitch.conf.pacnew /etc/nsswitch.conf
and it's all fixed. thanks!
great forum ! thanks
Last edited by virtual-travels (2017-07-11 08:46:04)
Offline
Please note that, while moving the pacnew in this instance fixed your problem, that is not standard practice. You should compare the file with it's pacnew, and merge the changes.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
In this case the only change that I had was the workaround I inserted, so it made sense to just use the package-supplied file verbatim. I should have clarified that I don't think that's a good practice for dealing with .pacnew files universally.
Offline
Thanks for clarifying.
Please remember to mark your thread as solved by editing the first post and amending your topic title.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
thanks, was not aware of this convention
Offline