FS#66957 - [systemd-resolvconf]dual stack - only ipv6 dns in resolv.conf
Attached to Project:
Arch Linux
Opened by C. Dominik Bódi (osginyast) - Tuesday, 09 June 2020, 16:43 GMT
Last edited by Toolybird (Toolybird) - Monday, 25 September 2023, 08:29 GMT
Opened by C. Dominik Bódi (osginyast) - Tuesday, 09 June 2020, 16:43 GMT
Last edited by Toolybird (Toolybird) - Monday, 25 September 2023, 08:29 GMT
|
Details
This is a follow-up from
https://bugs.archlinux.org/task/66308
The core of the issue seems to be fixed now in dhcpcd. However systemd-resolvconf still doesnt seem to get this right. Description: I have a netctl ethernet-dhcp config like this: Description='Ethernet' Interface=enp116s0 Connection=ethernet IP=dhcp IP6=dhcp Starting the interface, I would expect both IPv4 and IPv6 dns server to be added to /etc/resolv.conf. However, only the IP6 dns server is found in /run/systemd/resolve/resolv.conf I am using systemd-resolved with systemd-resolvconf installed. With openresolv, this works fine. Ideally, netctl would set up DNS so that both IPv4 and IPv6 dns servers are usable. When setting IP6 to stateless, only IPv4 DNS server shows up in resolv.conf Additional info: * netctl version 1.23-1 * systemd version 245.6-4 * systemd-resolvconf version 245.6-4 Steps to reproduce: 1. Install systemd-resolvconf 2. Create symlink /etc/resolv.conf -> /run/systemd/resolve/stub-resolv.conf 3. Enable and start systemd-resolved 4. Set up a dual-stack ethernet config file with both IP=dhcp and IP6=dhcp 5. netctl start <interface> 6. Check resolv.conf - Only IPv6 dns server shows up in resolv.conf 7. change IP6=stateless 8. netctl restart <interface> 9. Check resolv.conf - Only IPv4 dns server shows up in resolv.conf Regards, |
This task depends upon
Closed by Toolybird (Toolybird)
Monday, 25 September 2023, 08:29 GMT
Reason for closing: Upstream
Additional comments about closing: Failing to see how this is an Arch packaging issue. If still happening, please report upstream.
Monday, 25 September 2023, 08:29 GMT
Reason for closing: Upstream
Additional comments about closing: Failing to see how this is an Arch packaging issue. If still happening, please report upstream.
Regards,