Static route required when using domain overrides in DNS forwarder over IPsec VPN

Hi Manuel, not sure if this is a bug report, or a feature request. :)

In the past, a static route was required for remote sysloging to a syslog
server over a IPsec VPN. In recent versions of m0n0wall you added a check box
"Bind to LAN interface only" on the log settings tab which alleviated the need
for the static route.

I just ran across a similar situation where we have remote sites connected via
IPsec VPNs and need them to use our central DNS server for systems in our domain.

Setting up the domain override at a remote site to point at our central dns
server does not work unless we add the static route like we had to do with
sysloging in the past.

Do you think this is fixable within the dnsmasq integration of m0n0wall, or
will we be required to keep a static route when using the domain override
feature at remote sites?

Thanks!

--
Bill Arlofski
Reverse Polarity, LLC