Note I am a huge fan of dnsmasq, however, have you looked at unbound
also? I *think* it may have an option to force TCP upstream queries,
it's not clear, but I would assume this means it receives on UDP and
queries upstream on TCP (the documentation states "this may be helpful
for tunnelling situations")
You could even incorporate both dnsmasq and unbound in order to have
only a portion of your requests take this route? (another option is to
write a simple DNS server in say perl and do whatever you wish, using
a local dnsmasq/unbound/something else as your upstream proxy)
How "resource-hungry" is unbound?
The thing I like about dnsmasq is that it is very light and quite
happily functions in very resource-constrainted environments. The
environment within which dnsmasq is currently deployed is an old (though
versatile) router with 64mb RAM and 512mb flash memory (which is quite
old, so I am conscious of doing excessive writing on it). Even though I
am using this router for everything which passes through the network, I
cannot really expand and add packages too much simply because there is
nowhere to fit these in.
_______________________________________________
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
