[Dnsmasq-discuss] question on dnsmasq capability...trying to do something maybe a bit unusual

[Chris Friesen]

On 06/11/2010 01:53 PM, clemens fischer wrote:

> I don't think this type of wildcard is implemented directly.

Thats what it seemed to me as well.  Perhaps it should be explicit
rather than the current implicit assumption.

> If
> internal hosts of example.com had a common label "int", though, it would
> be:
> 
>     server=/example.com/#
>     server=/int.example.com/a.b.c.d

Not an option in my case.

> If not, you could try to list all the internal hosts manually:
> 
>     server=/example.com/#
>     server=/h1.example.com/a.b.c.d
>     server=/h2.example.com/a.b.c.d
>     server=/h3.example.com/a.b.c.d

Not an option.  This is a large corporation with thousands of hosts.

> Here the world visible wellknownX hosts are resolved from upstream
> forwarders while less specific queries go to a.b.c.d.

Right.  The problem in my case is that "example.com" is itself a
wellknown host, but I want anything *else* on that domain to be routed
to a private server.

Chris