On 07/31/2010 07:18 AM, Tim wrote:
On Fri, 2010-07-30 at 06:23 -0500, Robert Nichols wrote:
> Word from the developers is that one of the goals for NetworkManager
> 0.8.2 is support for a local caching resolver. That should eliminate
> the need for my workaround.
I hope they do mean merely adding support for it, rather than building
more into it.
Though I have to say that I have no problems with NetworkManager and
using a local name server. Of course my DHCP server, properly, doles
out the DNS address that the client should use.
I'm referring to a caching resolver running on the local machine, i.e.
127.0.0.1, not a nameserver running somewhere else on a local network.
The various messages I've read on this list seem to deal with
people
half using DHCP, wanting to override some of the settings. i.e. Not use
the DNS server address, and/or other details, supplied from the DHCP
server.
There's two approaches to resolving that: Have their DHCP server
provide the wanted addresses, properly. Or have their DHCP client
overrides configured, properly.
When I'm connecting via the WiFi hotspot at some local business, the
DHCP server is not under my control. NetworkManager invokes dhclient
with a custom config file that NetworkManager generates anew for
each invocation, and no customization of that configuration is
possible.
--
Bob Nichols "NOSPAM" is really part of my email address.
Do NOT delete it.