Notes |
(0000008)
disi (reporter)
2010-05-25 08:14
|
The idea is great.
Which ones? Google and OpenDNS are the one I can think of. |
|
(0000009)
viridior (administrator)
2010-05-25 08:42
|
interesting, I've never thought about it much less implemented. I'll look into it. |
|
(0000010)
viridior (administrator)
2010-05-25 08:49
|
looking around and thinking about this. Our intention was to use NetworkManager (fallback wicd) to handle our networking, in fact that is one of the things I'll be working on next for 0.3.0_rc4. Right now you will notice that I am using Gentoo's /etc/conf.d/net One of the things I turned on with NetworkManger was use of OpenResolv which provides more dynamic use of /etc/resolv.conf I would assume that I can configure it to use the contents of the attached file as defaults and then it will also get appended with whatever DNS servers come with a DHCP request.
I was going to put this on a lower priority but since I think I can wrap this up with my overall work with NetworkManager I will try to implement this at the same time. |
|
(0000011)
lamawithonel (reporter)
2010-05-25 13:52
|
However it's implemented, I defiantly think some fallback nameservers are a good idea. Even if I do get a reliable dhcp response, which is not always, I still worry about dns filtering, cache poisoning and update/propagation latency and reliability.
As for the file reasoning, for one I"m a config file guy who hasn't used NM for years and only recently started using wicd because wireless can be a pain. And two, resolv.conf is standard across most posix platforms so I figure it's a good place to keep comments and pointers; you might include in the resolv.conf.head file the line
"Neuvoo uses NetworkManager by default. You may make changes here, but it's suggested you use that tool first.,"
or some such. |
|
(0000018)
javaJake (administrator)
2010-06-07 00:48
|
I'd like to do as little configuration as possible. Here is an idea: we coul put a note into the installation guide and suggest additions to resolv.conf.head.
Thoughts? |
|
(0000019)
viridior (administrator)
2010-06-08 14:10
|
There is a line that we haven't really quantified yet on what we want to provide as far as system functionality vs. bloat.
On one hand there is a point to be made that adding too many custom configs/programs detracts from providing a lithe system that allows the user to customize to his/her personal taste. However, on the flip side if we don't do anything but minimal configs I don't see how we are really providing anything beyond a binrepo.
Nothing wrong with telling people to go to the wiki to add more functionality to their system but I think it would be counterproductive to make it a requirement to go through an extensive wiki setup guide just to make the system work (how well we want it to "work" is part of this discussion).
I personally have no preference as this applies to /etc/resolv.conf.tail, but this points to a larger issue that we need to talk and come to terms with so we can start binning issues that come up appropriately... if that is adding a pkg/config/patch to the future baselines or pushing the resolution to a wiki topic. |
|
(0000097)
javaJake (administrator)
2010-07-27 23:27
|
Enabling resolvconf for NetworkManager. Configuration of resolvconf can be left to users, especially when it comes to what DNS servers they trust. (It's pretty simple, so I don't think it even warrants a wiki page. Small release note might be good.) |
|
(0000107)
viridior (administrator)
2010-08-17 16:45
|
moving this to 0.4.0 as a potential improvement to user experience. |
|