<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'><pre>Kevin,<br><br>I don't think there is a flaw in your logic. You are probably 50% right. <br>DNSMASQ is so flexible and useful it has found two significant homes and<br>a bunch of other neat uses. <br><br>Top however, (1) as a single point entry router caching DNS <br>(ex 192.168.1.1 / X.X.X.X -> 8.8.4.4), and (2) as a local machine <br>name cache daemon (ex 127.0.1.1 / 192.168.1.2 -> 192.168.1.1). <br>For use (1) your default concept is quite right to avoid harassing the<br>world net and not enumerate your internal system to the world. For (2) <br>rather, the workstation will need to forward otherwise useless requests <br>up to the router to resolve local. So thats going to be your 50% split.<br><br>So I would recommend that both options be included in the CONF syntax.<br>I would then recommend that the default behavior be a conditional<br>compile for the distribution builder. In a Debian-Linux workstation<br>distr. the default is to forward. In a OpenWRT distr. the default is<br>to not forward bogus local ... something like that.<br><br>Eric<br><br>>Hi Simon & list,
>
>Ok, here's the controversial idea. Can we consider enabling
>'bogus-priv' by default and have an additional option say 'allow-priv'
>to now disable?
>
>My feeling is that not forwarding 'link-local' type requests upstream by
>default is a cleaner way of having things configured. Bearing in mind
>the popularity of dnsmasq in all sorts of devices (Internet of Things) a
>'be kind to your upstream servers and don't ask daft questions' default
>should at least be considered.
>
>I'm sure the flaws in my idea, logic and thinking will now be loudly
>explained :-)
>
>Kind regards,
>
>Kevin</pre> </div></body>
</html>