Comment 17 for bug 651007
Revision history for this message
| MarcH (marc-h38) wrote Re: Does not correctly write resolv.conf | #17 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
"use the DNS servers from the VPN" does NOT imply: "ignore the local DNS servers". Why would it? In *your* case the local DNS servers become unreachable, but not in mine. So in my case it is the command line client which is "buggy"
It is expected for some DNS servers to be not responsive: this is exactly why several of them should be configured.
This more and more looks like a glibc problem, not really related to NM. It is hard to ask NM to try to work around every limitation of the resolver in glibc. Suppose for a second that the resolver in glibc were to:
- re-read any change to resolv.conf immediately
- support more than 3 servers
- query all of them simultaneously and return as soon as it gets an answer
... then would you still have a problem? Looks like not!
If you find glibc resolver too limited, then try dnsmasq or an alternative resolver as you were suggested?