Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#54336 - [systemd] DNS resolution does not work

Attached to Project: Arch Linux
Opened by Brandon Gottlob (bnasty) - Wednesday, 07 June 2017, 02:14 GMT
Last edited by Christian Hesse (eworm) - Tuesday, 04 July 2017, 20:40 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Dave Reisner (falconindy)
Christian Hesse (eworm)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
systemd version 233-4, the current version in the [testing] repo seems to break DNS resolution. As a result, I can't connect to the Internet or any web sites by URL. Pinging by IP address both on my LAN and the public web does work. Additionally, the drill command works. However, pinging a domain name will fail. I have attached output from the ping and drill commands to demonstrate the issue.

Additional info:
* package version(s): systemd-233-4 libsystemd-233-4 systemd-sysvcompat-233-4
* my [testing] repo forum post: https://bbs.archlinux.org/viewtopic.php?id=226546

Steps to reproduce:
Switching to the packages systemd-233-4, libsystemd-233-4, and systemd-sysvcompat-233-4 caused DNS resolution to break. Reverting back to systemd-232-8, libsystemd-232-8, and systemd-sysvcompat-232-8 "fixes" the issue.
   ping_and_drill_out.txt (1.3 KiB)
This task depends upon

Closed by  Christian Hesse (eworm)
Tuesday, 04 July 2017, 20:40 GMT
Reason for closing:  Works for me
Comment by Brandon Gottlob (bnasty) - Monday, 03 July 2017, 09:47 GMT
Update: This is still an issue with systemd 233-6 in the [core] repo
Comment by Christian Hesse (eworm) - Monday, 03 July 2017, 09:56 GMT
Please give more information about your system.
Is systemd-resolved running? What do /etc/resolv.conf and /etc/nsswitch.conf look like?
Comment by Evangelos Foutras (foutrelis) - Monday, 03 July 2017, 10:00 GMT
Fix your nsswitch.conf file according to the wiki: https://wiki.archlinux.org/index.php/Avahi#Hostname_resolution

Can't just throw the mdns stuff in the middle of "resolve [!UNAVAIL=return]" and expect it to work.
Comment by Brandon Gottlob (bnasty) - Monday, 03 July 2017, 10:36 GMT
systemd-resolved was not running, neither in version 232-8 when DNS was working properly nor in 233-6. However, it looks like starting/enabling it fixes this issue in 233-6. A simple fix I've overlooked. Appreciate the help.

I've posted my /etc/resolv.conf and /etc/nsswitch.conf for good measures.
   confs (0.7 KiB)
Comment by Evangelos Foutras (foutrelis) - Monday, 03 July 2017, 10:47 GMT
Is it really that hard to fix your nsswitch.conf? The [!UNAVAIL=return] goes right after resolve, not wherever it looks the cutest.

Look at the wiki again and put everything in their proper place. It should work fine regardless of resolved running or not.

Loading...