Thomas,
>You say that your setup is "partially" fixed. What part is not fixed?
When I initially applied pdf's fix, I was able to resolve external
domains, but not internal domains. However, this seems to have resolved
itself, so now it seems my setup is completely fixed.
Also, the output of those commands are:
user@localhost:~$ debconf-show resolvconf
debconf: DbDriver "passwords" warning: could not open
/var/cache/debconf/passwords.dat: Permission denied
* resolvconf/downup-interfaces:
* resolvconf/linkify-resolvconf: false
* resolvconf/link-tail-to-original: false
resolvconf/fixing-immutable:
resolvconf/reboot-recommended-after-removal:
user@localhost:~$ who -b
system boot 2012-05-31 20:09
user@localhost:~$ ls -l /etc/resolv.conf
lrwxrwxrwx 1 root root 29 May 22 10:33 /etc/resolv.conf ->
../run/resolvconf/resolv.conf
user@localhost:~$ lsattr /etc/resolv.conf
lsattr: Operation not supported While reading flags on /etc/resolv.conf
user@localhost:~$ ls -l /run/resolvconf
total 4
-rw-r--r-- 1 root root 0 May 31 20:09 enable-updates
drwxr-xr-x 2 root root 60 Jun 1 10:01 interface
-rw-r--r-- 1 root root 97 Jun 1 10:01 resolv.conf
user@localhost:~$ ls -l /run/resolvconf/interface
total 4
-rw-r--r-- 1 root root 67 Jun 1 10:01 NetworkManager
user@localhost:~$ for F in /run/resolvconf/interface/* ; do echo "=== $F ===" ;
cat "$F" ; done
=== /run/resolvconf/interface/NetworkManager ===
domain mydomain.com
search mydomain.com
nameserver 127.0.0.1
user@localhost:~$ 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
domain mydomain.com
search mydomain.com
nameserver 10.157.10.12
nameserver 10.157.10.14
nameserver 192.168.1.1
user@localhost:~$ cat /etc/NetworkManager/NetworkManager.conf
[main]
plugins=ifupdown,keyfile
dns=dnsmasq
[ifupdown]
managed=false
user@localhost:~$ cat /run/nm-dns-dnsmasq.conf
server=10.157.10.12
server=10.157.10.14
server=192.168.1.1
user@localhost:~$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda2 152180736 87537376 57024220 61% /
udev 3935756 4 3935752 1% /dev
tmpfs 1579044 928 1578116 1% /run
none 5120 0 5120 0% /run/lock
none 3947600 612 3946988 1% /run/shm
cgroup 3947600 0 3947600 0% /sys/fs/cgroup
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1000244
Title:
resolv.conf not populated because /etc/resolv.conf symlink was not
created
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1000244/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
