I'm doing nothing but stirring up trouble around here, I tell ya...

Okay, a quick topography lesson here - I have two nics in each of the boxes in my data center, one is a 10/100 (fxp0) and a gigabit nic (re0). I have the 10/100 interface plugged into our publically accessible vlan, which is (for the most part) on our dedicated 10/100 managed core switch.

re0 is plugged into our backends vlan, with a private IP address block and is mostly on our managed gigabit switch.

So, pretty simple, right? Go into Bind's module, edit the config, set the " Default master server IP for remote slave zones" value to the private IP address of the Virtualmin server, and all is well, backend traffic stays on the gigabit network.

Well...then I decided to get smart, and put a remote DNS server at another site, and the spoilage I'm feeling from not having to manually update named.conf on remote boxes is huge. :) Everything works great until the zone transfer are attempted, at which point I smack my forehead and realize they're trying to pull from a remote master on a private IP address. d'oh!

Is there a right way to assign the remote master IP on a per-server basis, or is this a job for mad perl hacking skillz? :D

(It may be that I just run a cron job that does a search and replace in named.conf for the private IP and replace it with the public one, but that's a kludge. Needs to originate from Virtualmin I think).

File under Feature Requests?