I'm running a local copy of bind9 so that I can easily manage/resolve all of the machines on my internal net. I've been doing this for many years.
In general it works well. However, Netflix, Google, etc. have a tendency to have caches local to the ISPs network (for large ISPs) that are much closer, network-wise. To resolve external hosts to those caches I need to use my ISP's nameserver. I thought I had it figured out. I have a zone file for my internal network, with 'type master', and in the options I have configured a 'forwarders' statement that specifies the ISP nameserver. But it doesn't work. It ALWAYS defers to the ISP nameserver. The two seem to be at odds... Supposedly a zone type 'master' means The server reads the zone data direct from local storage (a zone file) and provides authoritative answers for the zone. But the forwarders option only has two modes - only or first: If set to 'only' the server will only forward queries, if set to 'first' (default) it will send the queries to the forwarder and if not answered will attempt to answer the query. WHat I want is the opposite behavior. I want to forward only if not resolved by the zone file(s) I'm providing. It might be acceptable if the 'first' mode worked, but besides the fact that it doesn't seem to, I have different results for some hosts depending on whether it's incoming or internal (via port forwarding on the router). This doesn't seem unreasonable. Is there anyone on the list a bit more expert WRT bind9 that can help me figure this out? john- _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
