[Bug 1816530] Re: DNS servers are not being set in the system correctly when you upgrade from 16.04 to 18.04

[Zoltán Süle]

Hi Dan,

first of all thank you for your time!!!

I added the "nameserver 8.8.8.8" line to the
/etc/resolvconf/resolv.conf.d/head and it adds this line to the
/etc/resolv.conf file

I removed the 8.8.8.8 line, restarted the computer and I have internet.

--------

$ ls -l /etc/resolv.conf
lrwxrwxrwx 1 root root 29 Aug  4  2016 /etc/resolv.conf -> ../run/resolvconf/resolv.conf


$ 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
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.

nameserver 127.0.0.53
search home


$ systemd-resolve --status

Global
          DNS Domain: home
          DNSSEC NTA: 10.in-addr.arpa
                      16.172.in-addr.arpa
                      168.192.in-addr.arpa
                      17.172.in-addr.arpa
                      18.172.in-addr.arpa
                      19.172.in-addr.arpa
                      20.172.in-addr.arpa
                      21.172.in-addr.arpa
                      22.172.in-addr.arpa
                      23.172.in-addr.arpa
                      24.172.in-addr.arpa
                      25.172.in-addr.arpa
                      26.172.in-addr.arpa
                      27.172.in-addr.arpa
                      28.172.in-addr.arpa
                      29.172.in-addr.arpa
                      30.172.in-addr.arpa
                      31.172.in-addr.arpa
                      corp
                      d.f.ip6.arpa
                      home
                      internal
                      intranet
                      lan
                      local
                      private
                      test

Link 5 (virbr0-nic)
      Current Scopes: none
       LLMNR setting: yes
MulticastDNS setting: no
      DNSSEC setting: no
    DNSSEC supported: no

Link 4 (virbr0)
      Current Scopes: none
       LLMNR setting: yes
MulticastDNS setting: no
      DNSSEC setting: no
    DNSSEC supported: no

Link 3 (wlp2s0)
      Current Scopes: none
       LLMNR setting: yes
MulticastDNS setting: no
      DNSSEC setting: no
    DNSSEC supported: no

Link 2 (eno1)
      Current Scopes: DNS
       LLMNR setting: yes
MulticastDNS setting: no
      DNSSEC setting: no
    DNSSEC supported: no
         DNS Servers: 195.34.133.21
                      212.186.211.21
          DNS Domain: home


$ grep . /run/resolvconf/interface/*
nameserver 127.0.0.53
search home


$ SYSTEMD_LOG_LEVEL=debug systemd-resolve google.com

Bus n/a: changing state UNSET → OPENING
Bus n/a: changing state OPENING → AUTHENTICATING
Resolving google.com (family *, interface *).
Bus n/a: changing state AUTHENTICATING → HELLO
Sent message type=method_call sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=Hello cookie=1 reply_cookie=0 signature=n/a error-name=n/a error-message=n/a
Got message type=method_return sender=org.freedesktop.DBus destination=:1.133 path=n/a interface=n/a member=n/a cookie=1 reply_cookie=1 signature=s error-name=n/a error-message=n/a
Bus n/a: changing state HELLO → RUNNING
Sent message type=method_call sender=n/a destination=org.freedesktop.resolve1 path=/org/freedesktop/resolve1 interface=org.freedesktop.resolve1.Manager member=ResolveHostname cookie=2 reply_cookie=0 signature=isit error-name=n/a error-message=n/a
Got message type=method_return sender=:1.1 destination=:1.133 path=n/a interface=n/a member=n/a cookie=15 reply_cookie=2 signature=a(iiay)st error-name=n/a error-message=n/a
google.com: 172.217.21.110

-- Information acquired via protocol DNS in 13.3ms.
-- Data is authenticated: no
Bus n/a: changing state RUNNING → CLOSED

--------

it seems the problem is solved.
The question is whether the patch/fix/change is included into that ISO file which is used for upgrading the older ubuntu releases to the 18.04?
I had many updates the last year, but the origin of the problem was that I couldn't connect to the internet right after the upgrade and this way I couldn't update any packages or configuration..

-- 
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/1816530

Title:
  DNS servers are not being set in the system correctly when you upgrade
  from 16.04 to 18.04

Status in resolvconf package in Ubuntu:
  Incomplete

Bug description:
  I upgraded my 16.04 to 18.04 before the official release. After the
  upgrade I noticed that I don't have internet access. The wired network
  and the wifi settings looked good, but the internet didn't work. After
  the login the system always switched itself into airplane mode. I
  tethered the network via USB and Bluetooth by my mobile but they also
  didn't work.

  I found a useful answer from @andrew-woodhead666:
  https://answers.launchpad.net/ubuntu/+question/665374

  it seems this bug is still not fixed for the upgraded dists in the main release and affects a few dozens of ubuntu users.
  https://askubuntu.com/questions/1021884/no-internet-after-upgrade-from-16-04-to-18-04

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