Hi Mats; On Sunday 16 March 2008 19:50:59 Mats Erik Andersson wrote: > Hello all, > > in revising my own code in the Webconf package dnsmasq.lwp > an issues comes to my mind. There is one adaption of the > file /etc/dnsmasq.conf that the buildsystem of Bering implements: > > domain=private.network > > with well known intentions. However, the logically accompanying > option > > local=/private.network/ > > is NOT implemented. Short reminder: this option prevents DNS-questions > concerning the domain "private.network" to be forwarded upstreams.
You are correct; it does generate unnecessary traffic and load on the upstream servers. So let's play nice and correct it. > I have used this mechanism myself for a long time, but now I am > convinced that this option ought to be present alongside the "Domain" > setting in the future webconf page dnsmasq.cgi. > > My suggestion is therefore to add a standard mechanism in the script > > dhcpcd/buildtool.mk I assume, that should be read as "dnsmasq/buildtool.mk". > that implements this insertion. I could, however, imagine one argument > against my suggestion: "Now the new user has another setting to change > before he runs the new firewall machine". But, granted that my code to > care for "domain" and "local" in the basic webconf page dnsmasq.cgi will > not be declined, the new user will be aware of both settings, and hence > will se their cooperation clearly enough. > > Please comment on this. Most users will be happy with the default; and those who want to change, can either rely on your upcoming page or change it twice. Even those who don't care won't see an error, it's just the same behaviour as today. kp ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ leaf-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/leaf-devel
