[Bug 1180406] Re: [Saucy] DNS issues when resolvconf is installed

[Thomas Hood]

Please reinstall resolvconf, reboot, and then post the output of the
following commands.

ls -l /etc/resolv.conf
cat /etc/resolv.conf
ls -l /run/resolvconf
ls -l /run/resolvconf/interface
for F in /run/resolvconf/interface/* ; do echo === $F === ; cat $F ; done
ls -l /etc/resolvconf/resolv.conf.d
for F in /etc/resolvconf/resolv.conf.d/* ; do echo === $F === ; cat $F ; done
cat /etc/NetworkManager/NetworkManager.conf
nm-tool

** Changed in: resolvconf (Ubuntu)
       Status: New => Incomplete

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

Title:
  [Saucy] DNS issues when resolvconf is installed

Status in “resolvconf” package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  This morning I upgrade my system. After having rebooted it, web addresses are no longer resolved.
  I can still ping servers and if I add entries in /etc/hosts it works fine.
  I tested with my both network cards (eth and wlan) but I still have this bug with the DNS. But it seems it's not due to the DNS server that I'm using because if I test with another computer on the same network, I don't have any problem. I also tried with a public DNS but I still have the same problem.

  This is what I installed and upgraded this morning:

  Install: linux-headers-3.9.0-2-generic:amd64 (3.9.0-2.6, automatic),
  linux-image-extra-3.9.0-2-generic:amd64 (3.9.0-2.6, automatic), linux-
  image-3.9.0-2-generic:amd64 (3.9.0-2.6, automatic), linux-
  headers-3.9.0-2:amd64 (3.9.0-2.6, automatic)

  Upgrade: libkrb5-3:amd64 (1.10.1+dfsg-5, 1.10.1+dfsg-6),
  libk5crypto3:amd64 (1.10.1+dfsg-5, 1.10.1+dfsg-6), doc-base:amd64
  (0.10.4, 0.10.5), linux-generic:amd64 (3.9.0.1.2, 3.9.0.2.3),
  seahorse-nautilus:amd64 (3.7.5-0ubuntu1, 3.8.0-0ubuntu1),
  libkrb5-dev:amd64 (1.10.1+dfsg-5, 1.10.1+dfsg-6), libgssrpc4:amd64
  (1.10.1+dfsg-5, 1.10.1+dfsg-6), libkrb5support0:amd64 (1.10.1+dfsg-5,
  1.10.1+dfsg-6), libspandsp2:amd64 (0.0.6~pre20-3ubuntu1,
  0.0.6~pre20-3.1), python3-urllib3:amd64 (1.5-0ubuntu1, 1.6-1), linux-
  headers-generic:amd64 (3.9.0.1.2, 3.9.0.2.3), linux-image-
  generic:amd64 (3.9.0.1.2, 3.9.0.2.3), libkadm5clnt-mit8:amd64
  (1.10.1+dfsg-5, 1.10.1+dfsg-6), libkadm5srv-mit8:amd64 (1.10.1+dfsg-5,
  1.10.1+dfsg-6), krb5-locales:amd64 (1.10.1+dfsg-5, 1.10.1+dfsg-6),
  libkdb5-6:amd64 (1.10.1+dfsg-5, 1.10.1+dfsg-6), linux-libc-dev:amd64
  (3.9.0-1.5, 3.9.0-2.6), krb5-multidev:amd64 (1.10.1+dfsg-5,
  1.10.1+dfsg-6), libgssapi-krb5-2:amd64 (1.10.1+dfsg-5, 1.10.1+dfsg-6)

  (no more installation/upgrade during this session)

  I also tried to removed this line 'dns=dnsmasq' in
  /etc/NetworkManager/NetworkManager.conf (and restarted NM) but I still
  had this bug.

  After having removed resolvconf package (and rebooted) I no longer
  have this bug.

  Any idea?

  PS: I'm not using a vpn or proxy and I didn't change options in .conf
  files about the network.

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