[Bug 1710666] Re: No resolution until manually adding a nameserver to resolv.conf

Dimitri John Ledkov launchpad at surgut.co.uk
Mon Aug 21 12:28:28 UTC 2017


I am very glad to hear this =)

That would be these changes:
  * Set UseDomains to true, by default, on Ubuntu.
    On Ubuntu, fallback DNS servers are disabled, therefore we do not leak queries
    to a preset 3rd party by default. In resolved, dnssec is also disabled by
    default, as too much of the internet is broken and using Ubuntu users to debug
    the internet is not very productive - most of the time the end-user cannot fix
    or know how to notify the site owners about the dnssec mistakes. Inherintally
    the DHCP acquired DNS servers are therefore trusted, and are free to spoof
    records. Not trusting DNS search domains, in such scenario, provides limited
    security or privacy benefits. From user point of view, this also appears to be
    a regression from previous Ubuntu releases which do trust DHCP acquired search
    domains by default.
    Therefore we are enabling UseDomains by default on Ubuntu.
    Users may override this setting in the .network files by specifying
    [DHCP|IPv6AcceptRA] UseDomains=no|route options.
  * resolved: create private stub resolve file for integration with resolvconf.
    The stub-resolve.conf file points at resolved stub resolver, but also lists the
    available search domains. This is required to correctly resolve domains without
    using resolve nss module.
  * Enable systemd-resolved by default
  * Create /etc/resolv.conf at postinst, pointing at the stub resolver.
    The stub resolver file is dynamically managed by systemd-resolved. It points at
    the stub resolver as the nameserver, however it also dynamically updates the
    search stanza, thus non-nss dns tools work correctly with unqualified names and
    correctly use the DHCP acquired search domains.
  * libnss-resolve: do not disable and stop systemd-resolved
    resolved is always used by default on ubuntu via stub resolver, therefore it
    should continue to operate without libnss-resolve module installed.

>From the 234-2ubuntu1, which only just migrated =) See:

https://launchpad.net/ubuntu/+source/systemd/+changelog

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

Title:
  No resolution until manually adding a nameserver to resolv.conf

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  I have no resolution until I manually add a `nameserver 8.8.8.8` to
  `/run/resolvconf/resolv.conf`.

  And if `resolvconf` is not installed, I don't know how to add a
  nameserver. So I keep that installed.

  I'm using Network Manager and it should take care of adding
  nameservers.

  I don't know where what is going wrong.

  I'm willing to send any necessary info from this system.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 233-8ubuntu3
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Aug 14 18:58:10 2017
  InstallationDate: Installed on 2010-10-12 (2498 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MachineType: Supermicro X10SRA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-13-generic root=/dev/mapper/root ro nomdmonddf nomdmonisw nomodeset
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-04-29 (107 days ago)
  dmi.bios.date: 06/23/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.0a
  dmi.board.asset.tag: Default string
  dmi.board.name: X10SRA
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0a:bd06/23/2016:svnSupermicro:pnX10SRA:pvr0123456789:rvnSupermicro:rnX10SRA:rvr1.01:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.name: X10SRA
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

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



More information about the foundations-bugs mailing list