This works, at least at the base level. Now we will need to figure out the tuning (e.g. how many threads, what port for unbound-control...) in each running instance. Currently I have it setup for 8 threads, 3 in one instance, 3 in another, and two in another.
So now based upon a from IP, it pays attention to the appropriate (one of three) configs file. All three are listening at the same time.
Bruce
Bruce Hayward, MTS Allstream Inc., (p) 204-958-1983 (e) bruce.hayward@mtsallstream.com
It seems to work out for you, but I wanted to explain the config syntax.
If you enable: interface-automatic: yes then any interface ports
other than 53 disappear (when using interface: <ip address[@port]> as
per the documentation).
Yes it then ignores the interface-lines. (but not the
outgoing-interface lines).
Thoughts on how to accomplish both (views and anycast) given the
behaviour of ports on the <ip address[@port]> line teamed with
interface-automatic.
You can specify a different port using port: 12345 and that should work
with interface-automatic. There is no config syntax to make it listen
on multiple ports, though.