BIND configuration for internal and external views are very similar except your reverse look up are different. Search how to setup BIND for lan and wan. There are great examples online.
Essentially you need to have two zones and two reverse lookup zones. Here is a quick example from mine:
Code:
// excerpt of my LAN (internal)
zone "example.com" {
type master;
file "example.com.lan";
allow-update { none; };
};
zone "1.168.192.in-addr.arpa" {
type master;
file "1.168.192.in-addr.arpa.db";
allow-update { none; };
};
// excerpt of my WAN (external)
zone "example.com" {
type master;
file "example.com.wan";
allow-update { none; };
};
// replace xxx.xxx.xxx with your external IP network
zone "xxx.xxx.xxx.in-addr.arpa" {
type master;
file "xxx.xxx.xxx.in-addr.arpa.db";
allow-update { none; };
};
Also question about your setup (and I may have misunderstood you) but are you making a virtual instance as bind server? Why? What if the host goes down? You will loose all name resolution. I recommend using a physical box for things like dhcp and dns.
Hope this helps. Let me know if you have any questions.