|Summary:|| systemd-resolved: order of nameservers in dhcp lease is not respected|
|Status:||RESOLVED FIXED||QA Contact:||systemd-bugs|
|i915 platform:||i915 features:|
|Attachments:||tcpdump, resolv.conf and leases output|
Description nrocco 2015-05-16 11:47:48 UTC
Created attachment 115829 [details] tcpdump, resolv.conf and leases output I have the router on my lan configured to provide "Domain-Name-Server Option 6" with a list of dns servers to every client requesting a dhcp lease. The dns servers are listed in order of preference. I am trying to achieve that local dns server is the primary resolver for clients. In the attached txt file you can see some output of tcpdump, /etc/resolv.conf and /run/systemd/netif/leases/*. In my example 192.168.178.70 is my local dns server and 188.8.131.52 is my upstream dns server. No matter in what order my dhcp server serves the name server list in dhcp option 6 (see tcpdump output), systemd-networkd always puts the 184.108.40.206 on top in /etc/resolv.conf. I could not find any documentation describing this as expected behaviour.
Comment 1 Zbigniew Jedrzejewski-Szmek 2015-05-16 23:29:57 UTC
It helps to always specify exact version of the software being used. This should be fixed in git: http://cgit.freedesktop.org/systemd/systemd/commit/?id=822db23cfa.
Comment 2 nrocco 2015-05-17 20:44:00 UTC
How silly of me, I am using: $ cat /etc/os-release NAME="Arch Linux" ID=arch PRETTY_NAME="Arch Linux" ANSI_COLOR="0;36" HOME_URL="https://www.archlinux.org/" SUPPORT_URL="https://bbs.archlinux.org/" BUG_REPORT_URL="https://bugs.archlinux.org/" and $ pacman -Q systemd systemd 219-6 and not sure if it is relevant but I use wpa_supplicant to manage my wireless: $ % pacman -Q wpa_supplicant wpa_supplicant 1:2.3-1 Is that enough information?
Comment 3 Zbigniew Jedrzejewski-Szmek 2015-05-17 21:13:41 UTC
I'm don't use arch, but judging by https://projects.archlinux.org/svntogit/packages.git/tree/trunk?h=packages/systemd, that patch is not in 219-6. I think we can assume that it is indeed fixed in git. Please reopen if this is still an issue with systemd-220.
Comment 4 nrocco 2015-05-18 08:33:10 UTC
Hi Zbigniew Jedrzejewski-Szmek, Thanks for assistance. Appreciated. If v220 still does not 'solve' this I will reopen other wise we will consider it as fixed.