> That I've seen? Sort of: Just change the port dnsmasq's DNS > resolver listens on. Add, for instance: > > port=54 > > to your dnsmasq.conf, restart, and it should bind to 54 instead of > 53. Firewall off traffic to port 54, and it's invisible. > I don't recommend this action in general; I'm just using it in one > corner case where I have 31 zones being served up on the same box > as dnsmasq. While dnsmasq is awesome for local caching, it's not > designed for serving up lots of authoritative DNS (at least, not > that I've seen :-). >
Yes, that's the workaround i'm using right now. Thank you. However, My system is very tight (a floppy based firewall and router) and would be better to not run anything not needed. > Thanks to Simon for the great work, by the way. Sure, dnsmasq is great.
