Hi all! On Wed, May 16, 2007 at 09:53:09PM -0000, FreeWRT wrote: > We could define dns server to use for each interfaces. So fwifupdown could > be modified to add these entries to /etc/resolv.conf. If a device goes up > fwifupdown adds the entries for this device, if device goes down > fwifupdown should remove the added lines for this device.
Is this really what the whole DNS system is ment to be? I think: * all nodes having a static ip setup also have their static dns setup (i.e. resolv.conf entries) * all nodes needing a dynamic ip setup (mobile devices, e.g.) get their dns setup via the same technology they get the ip setup from (i.e. dhcp) * all routers (as our target devices potentially all are) will either fall into the first category defined here, or will even be part of the dns system of the subnet they provide. The latter is very likely, as private LANs seldomly make use of different machines for routing and dns. So for each of the cases above there should be no question about how resolv.conf comes to it's entries. Some additional points I came across: * how to handle dhcp clients? None of them supports intelligent editing of resolv.conf. * Who cares about the precedence of different nameserver entries? Having some entries with dead nameservers before any valid one actually causes big delays when resolving names. * What about domain and search entries? there must only exist a single domain entry (if any) inside resolv.conf. Multiple search entries could be added, but having a short name always completing to the wrong canonical name because of wrong order of search entries can be a pain in the ass, too. So if this is gonna be a vote, I vote for skipping this feature, as it's rather a bug. Greetings, Phil _______________________________________________ freewrt-developers mailing list [email protected] https://www.freewrt.org/lists/listinfo/freewrt-developers
