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

Wed May 15 15:58:13 UTC 2013

I just reinstalled resolvconf and rebooted and now, everything works
fine :)

  $ ls -l /etc/resolv.conf
   lrwxrwxrwx 1 root root 29 mai 15 17:44 /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
   nameserver 127.0.1.1

  $ ls -l /run/resolvconf
   total 4
   -rw-r--r-- 1 root root   0 mai 15 17:46 enable-updates
   drwxr-xr-x 2 root root  60 mai 15 17:46 interface
   -rw-r--r-- 1 root root 172 mai 15 17:46 resolv.conf

  $ ls -l /run/resolvconf/interface
   total 4
   -rw-r--r-- 1 root root 21 mai 15 17:46 NetworkManager

  $ for F in /run/resolvconf/interface/* ; do echo === $F === ; cat $F ; done
   zsh: == not found

  $ for F in /run/resolvconf/interface/* ; do echo "=== $F ===" ; cat $F ; done
   === /run/resolvconf/interface/NetworkManager ===
   nameserver 127.0.1.1

  $ ls -l /etc/resolvconf/resolv.conf.d
   total 8
   -rw-r--r-- 1 root root   0 déc 13 19:27 base
   -rw-r--r-- 1 root root 151 déc 13 19:27 head
   -rw-r--r-- 1 root root  51 mai 15 16:00 original
   -rw-r--r-- 1 root root   0 mai 15 17:44 tail

  $ for F in /etc/resolvconf/resolv.conf.d/* ; do echo === $F === ; cat $F ; done
   zsh: == not found

  $ for F in /etc/resolvconf/resolv.conf.d/* ; do echo "=== $F ===" ; cat $F ; done
   === /etc/resolvconf/resolv.conf.d/base ===
   === /etc/resolvconf/resolv.conf.d/head ===
   # 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
   === /etc/resolvconf/resolv.conf.d/original ===
   # Generated by NetworkManager
   nameserver 127.0.1.1
   === /etc/resolvconf/resolv.conf.d/tail ===

  $ cat /etc/NetworkManager/NetworkManager.conf
   [main]
   plugins=ifupdown,keyfile
   dns=dnsmasq

   [ifupdown]
   managed=false

  $ nm-tool

   NetworkManager Tool

   State: connected (global)

   - Device: eth0  [Auto] ---------------------------------------------------------
     Type:              Wired
     Driver:            atl1c
     State:             connected
     Default:           yes
     HW Address:        70:xx:xx:xx:xx:xx

     Capabilities:
       Carrier Detect:  yes
       Speed:           1000 Mb/s

     Wired Properties
       Carrier:         on

     IPv4 Settings:
       Address:         192.168.1.7
       Prefix:          24 (255.255.255.0)
       Gateway:         192.168.1.1

       DNS:             192.168.0.1
       DNS:             8.8.8.8

   - Device: wlan0 ----------------------------------------------------------------
     Type:              802.11 WiFi
     Driver:            rtl8192se
     State:             unavailable
     Default:           no
     HW Address:        1C:xx:xx:xx:xx:xx

     Capabilities:

     Wireless Properties
       WEP Encryption:  yes
       WPA Encryption:  yes
       WPA2 Encryption: yes

     Wireless Access Points

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