[Bug 1610479] Re: interface-order needs definitions for systemd predictable names

Suho Meso 1610479 at bugs.launchpad.net
Thu Oct 11 12:04:58 UTC 2018


Hi,

I've an issue using resolvconf in combination with rdnssd. The host is getting the nameserver stuff via RDNSS, not DHCPv6.
The interface order doesn't cover the rdnssd method?! Interface name should be ens3.

/run/resolvconf/interface/000.rdnssd:nameserver 2a02:...::47
/run/resolvconf/interface/000.rdnssd:nameserver 2a02:...::48
/run/resolvconf/interface/ens3.dhclient:domain abz.com
/run/resolvconf/interface/ens3.dhclient:search abz.com
/run/resolvconf/interface/ens3.dhclient:nameserver 10.x.x.47


root at host:/etc/resolvconf# cat /etc/network/interfaces
# Interface lo
auto lo
iface lo inet loopback
# Interface lo_ipv6
iface lo inet6 loopback
# Interface ens3
auto ens3
iface ens3 inet dhcp
# Interface ens3_ipv6
iface ens3 inet6 auto

root at host:/etc/resolvconf# dpkg -l | grep resolvconf
ii  resolvconf                          1.78ubuntu6                                all          name server information handler
root at host:/etc/resolvconf# dpkg -l | grep rdnssd
ii  rdnssd                              1.0.1-1ubuntu2                             amd64        IPv6 recursive DNS server discovery daemo

root at host:/etc/resolvconf# cat /etc/issue
Ubuntu 16.04.4 LTS \n \l

root at host:/etc/resolvconf# uname -a
Linux ermscn01 4.4.0-130-generic #156-Ubuntu SMP Thu Jun 14 08:53:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1610479

Title:
  interface-order needs definitions for systemd predictable names

Status in resolvconf package in Ubuntu:
  Confirmed

Bug description:
  Another release, another round of interface name changes.

  This time systemd has gotten into the fray to make things even more
  interesting.

  https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/

  As such, IPv4 resolvers are now being preferred over IPv6 again on
  these new interface names.

  kjotte at flounder:~$ grep '' /run/resolvconf/interface/ens3.*
  /run/resolvconf/interface/ens3.dhclient:search nivex.lan.
  /run/resolvconf/interface/ens3.dhclient:nameserver 172.31.3.30
  /run/resolvconf/interface/ens3.ip6.dhclient:search home.nivex.net.
  /run/resolvconf/interface/ens3.ip6.dhclient:nameserver fd60:e0:a0f4:121::10
  /run/resolvconf/interface/ens3.ip6.dhclient:nameserver fd60:e0:a0f4:321::4

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: resolvconf 1.78ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Fri Aug  5 19:53:25 2016
  InstallationDate: Installed on 2016-08-04 (1 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
  PackageArchitecture: all
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: resolvconf
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1610479/+subscriptions



More information about the foundations-bugs mailing list