On Wed, Nov 25, 2015 at 11:01 AM, John Meissen <[email protected]> wrote:
> > [email protected] said: > > WHat I want is the opposite behavior. I want to forward only if not > resolved > > by the zone file(s) I'm providing. > > Playing around some more shows it's working the way I want when resolving > requests from other machines on the network. It's only NOT doing it right > when > trying from the system that bind is running on (yes, the same instance is > listening on 127.0.0.1:53 and 192.168.nn.nn:53). So, if you try to use the resolver at the local IP from the machine it's running on (the non-localhost IP assigned to the machine - presumably 192.168.x.y - should work even if it is the same machine as localhost), does it work as intended? If so, perhaps you have BIND configured to react differently to queries from 192.168.x than "anywhere else" ? This article: https://www.digitalocean.com/community/tutorials/how-to-configure-bind-as-a-caching-or-forwarding-dns-server-on-ubuntu-14-04 shows a bit of the potential logic that matches how I've seen bind configured - some subnets get special treatment (search for 'goodclients') but you have to in effect opt-in localhost/localnet separately and explicitly. _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
