Comment 1 for bug 271542
Revision history for this message
| Gert van Dijk (gertvdijk) wrote Re: [intrepid] nameserver is not set (using wifi) | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Same problem here, with updated packages as of 2008-10-23. This seems the problem only for local networks. When connecting to my 802.1x university's network I get an external IP (130.x) and resolv.conf is updated fine. When connecting to local networks it will not and my resolv.conf is empty, despite NM shows clearly it's given the the addresses on dhcp!
syslog output when connecting to local network, shows three nameservers available.
Oct 23 16:24:31 gert-laptop NetworkManager: <info> nameserver '172.20.8.71'
Oct 23 16:24:31 gert-laptop NetworkManager: <info> nameserver '172.20.8.72'
Oct 23 16:24:31 gert-laptop NetworkManager: <info> nameserver '172.20.8.73'
Oct 23 16:24:31 gert-laptop NetworkManager: <info> domain name 'BalPol.Local'
resolv.conf file after connect shows only the line it's managed by Networkmanager. It does not matter if resolvconf is installed or not. If it is, the resolv.conf file will only show it's managed by resolvconf.
Additionally, when entering the nameservers manually in NM it won't appear in resolv.conf even then!
FYI: I have disabled avahi-daemon for (proper) use of the local network and it has worked well in Hardy.