Maybe Simon can figure out what you're saying, but I can't. If you included some specific examples it would make your situation much easier to understand.
e.g. (and if your situation doesn't substantially match this made-up example, go and re-read the description of the expand-hosts option) <<<Begin made-up example>>> /etc/hosts has an entry for the unqualified name xyzzy: aaa.bbb.ccc.71 xyzzy /etc/resolv.conf points to localhost first, then my ISP server 127.0.0.1 server aaa.bbb.ccc.ddd nslookup xyzzy works: > nslookup xyzzy Authoritative response from 127.0.0.1: aaa.bbb.ccc.71 (A record) nslookup xyzzy.domain.com also succeeds, but I think it shouldn't with expand-hosts turned off: > nslookup xyzzy.domain.com Authoritative response from 127.0.0.1: aaa.bbb.ccc.71 (A record) I want this to return NXDOMAIN instead. How can I configure dnsmasq to do that? <<<End made-up example>>> On Tue, Dec 28, 2010 at 12:34 AM, Jean-Pierre van Melis < [email protected]> wrote: > > I am having trouble with the feature expand-hosts. > The dnsmasq running on my router has no 'expand-hosts' in its dnsmasq.conf > and it still expands hosts for domains that are unable to resolve. > It is especially troublesome in my setup as I also have wildcard set on my > <domain> so these requests will be redirected to my WAN IP address. > > On my router I have a pound reverse proxy running which then gets traffic > which it shouldn't receive. > > Why is dnsmasq expanding the host? > It seems it does it always when I set <domain=domain.com>. Is this true? > If so, why is there a separate setting for expand-hosts? > > I understand the need for such a feature, but I don't understand why it > also expands on hosts that don't contain a dot. > > Is it possible to have a switch so I can better control its behavior? > > Cheers all... > > _______________________________________________ > Dnsmasq-discuss mailing list > [email protected] > http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss > >
