Axel Dörfler <"Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>> wrote:> "Waldemar Kornewald" <Waldemar.Kornewald@xxxxxx> wrote: > > Please do not forget that some interfaces want to set up a > > nameserver > > from > > kernel-level. ;) > > There should be some better way to set up the nameservers than > > writing an > > entry into resolv.conf like Syllable's dhcp. > > Why? It has to be read out everytime a DNS is to be resolved anyway > (at > least if we keep using it this way). Because you surely do not want to keep that DNS entry after you disconnect, the connection is lost, or your system crashes. ;) Alternatively, we could have a "/etc/dynamic-resolv.conf" which is cleared on boot-up. A more error-safe and easier system would still be better, IMHO. Why are dynamic/static attributes not good for this? The static attributes get saved (on each change) to /etc/netsettings or ~/config/settings/kernel/netsettings. There would be a nameservers section: nameservers { ipv4 129.24.234.12 ipv6 a:b:c:d:e:..... } # and maybe some other sections (not important, just to visualize my idea) interfaces { eth0 { ipv4 192.168.0.1 } } Dynamic attributes would only live in memory and never saved. A simple piece of code: dns_manager->RemoveAttributeAt(dns_manager->IndexOfValue("ipv4", mydns)); would remove that nameserver when the interface disconnects (for whatever reason). A system crash is no problem because the entries are not saved to disk. Thus, no need for clearing a file at boot-up. ;) Just a suggestion. :) This is roughly what I had in mind for DNS. Waldemar