Implications of BIND Forwarders
I've got forwarders set on the nameserver at work. Last week, I tried to delegate a subdomain to another nameserver and had a devil of a time. The problem was the forwarders; here is the solution:
zone "subdomain.example.com" in {
// ...
forwarders { };
};
Otherwise, the nameserver will ask the forwarders and not the delegate. Having learned this tidbit, my subconscious realized a few days later (i.e. today) that I could use this to my advantage in another seemingly unrelated situation.
My LAN at home is connected to work's LAN. At work, as well as at home, I have
split views for internal and external. You can use per-zone forwarders
clauses in situations like these to access work's internal view (without
becoming a slave) even though your normal forwarders are third parties such as
your ISP's name servers. Here is the config on my home box, in the internal
view:
zone "example.com" in {
type forward;
forwarders { 172.16.5.3; 172.16.59.7; };
forward only;
};


