Exactly the same problem here. Network Manager (or one of its helpers) seems to assume that the DHCP server is *always* a DNS caching server (i.e. that it will accept DNS queries on 53/UDP & 53/TCP, look up the results and return the resolved IP address to a client). This is by no means the case and is broken behaviour!
The router in the Net Cafe where I work (a fairly common NetGear DG824M) does not have a built in DNS server, but issues its upstream DNS servers to DHCP clients. Network Manager (or one of its helpers) blindly ignores these and instead puts 192.168.1.1 (my router's IP) into /etc/resolv.conf. Meanwhile, Windows & Mac wireless users connect effortlessly, whilst I have to edit /etc/resolv.conf each time I am allocated an IP address via DHCP. This is a serious problem - especially for those who roam networks - and it is still a problem on the most recent version of Gutsy as at today. The reason that there aren't more people reporting it is because most routers *do* act as DNS caching servers, but not all of them do and furthermore in some configurations this is not the desired configuration. Also, prepending DNS servers sounds like a horrible kludge which would get especially messy with roaming networks, requiring modifications each time one connected to a new roamed network (not to mention it probably incurs performance degradation in name resolution). We need Network Manager (or helpers) to do what the DHCP server tells it to which means to use the DNS server(s) it is given, and nothing else. -- resolv.conf overwritten no matter what I do https://bugs.launchpad.net/bugs/92761 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
