← Back to team overview

group.of.nepali.translators team mailing list archive

[Bug 1626617] Re: console-conf does not allow to set up dns for static ip

 

** No longer affects: snappy

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1626617

Title:
  console-conf does not allow to set up dns for static ip

Status in netplan:
  Fix Released
Status in nplan package in Ubuntu:
  Fix Released
Status in subiquity package in Ubuntu:
  Fix Released
Status in nplan source package in Xenial:
  Fix Released
Status in subiquity source package in Xenial:
  Won't Fix
Status in nplan source package in Yakkety:
  Fix Released
Status in subiquity source package in Yakkety:
  Won't Fix

Bug description:
  [Impact]
  subiquity and other nplan users may need to include DNS information when setting up a system.

  [Test case]
  1) set up a system with a netplan configuration including the nameserver: key for an interface, such as the following:

  network:
    ethernets:
      enxb827ebd3f20f:
        addresses: [192.168.0.200/24]
        nameservers: 192.168.0.10
    version: 2

  Verify that the nameserver settings are properly installed to the
  system (see /etc/resolv.conf or /run/systemd/resolve/resolv.conf)

  [Regression potential]
  Existing configurations that do not include nameserver configs should continue to work as-is; without nameserver data if using static addresses, or with the nameserver data retrieved from DHCP.

  [Original bug report]
  There's no way to setup DNS info for static IP configuration, which leads to broken name resolution:

  fgimenez@localhost:~$ cat /etc/netplan/00-snapd-config.yaml
  # This is the network config written by 'console-conf'
  network:
    ethernets:
      enxb827ebd3f20f:
        addresses: [192.168.0.200/24]
    version: 2
  fgimenez@localhost:~$ ping www.ubuntu.com
  ping: unknown host www.ubuntu.com
  fgimenez@localhost:~$ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  #     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN

  Selecting DHCP config from console-conf all works fine:

  fgimenez@localhost:~$ cat /etc/netplan/00-snapd-config.yaml
  # This is the network config written by 'console-conf'
  network:
    ethernets:
      enxb827ebd3f20f:
        addresses: []
        dhcp4: true
    version: 2
  fgimenez@localhost:~$ ping www.ubuntu.com
  PING www.ubuntu.com (91.189.90.59) 56(84) bytes of data.
  64 bytes from www.ubuntu.com (91.189.90.59): icmp_seq=1 ttl=51 time=34.0 ms
  64 bytes from www.ubuntu.com (91.189.90.59): icmp_seq=2 ttl=51 time=39.4 ms
  64 bytes from www.ubuntu.com (91.189.90.59): icmp_seq=3 ttl=51 time=37.0 ms
  ^C
  --- www.ubuntu.com ping statistics ---
  3 packets transmitted, 3 received, 0% packet loss, time 2003ms
  rtt min/avg/max/mdev = 34.066/36.882/39.496/2.221 ms
  fgimenez@localhost:~$ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  #     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  nameserver 192.168.0.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1626617/+subscriptions