search for: localhost_resolver

...med -t /var/named/chroot found 1 CPU, using 1 worker thread loading configuration from '/etc/named.conf' listening on IPv6 interface lo, ::1#53 listening on IPv4 interface lo, 127.0.0.1#53 command channel listening on 127.0.0.1#953 command channel listening on ::1#953 zone 0.in-addr.arpa/IN/localhost_resolver: loaded serial 42 zone 0.0.127.in-addr.arpa/IN/localhost_resolver: loaded serial 1997022700 zone 255.in-addr.arpa/IN/localhost_resolver: loaded serial 42 zone 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN/localhost_resolver: loaded serial 1997022700 zone localdomain/IN...

>From the manual, localnets matches hosts belonging to a network for which the server has an interface in. I have a dns server in a dmz with an ip of 192.168.2.2 in /24. Named.conf has 3 views, localhost_resolver -> localhost, internal -> localnets, and external -> !localnets; !localhost. I have a management workstation in 192.168.0.0/24 that is connecting and receiving the following debug: client 192.168.0.44#2188: no matching view in class 'IN' I don't get it? Obvioulsy if I add all...

...{ localhost; any; }; allow-query-cache { localhost; any; }; # allow-query { localhost; }; # allow-query-cache { localhost; }; }; logging { channel default_debug { file "data/named.run"; severity dynamic; }; }; view localhost_resolver { match-clients { localhost; any; }; match-destinations { localhost; any; }; # match-clients { localhost; }; # match-destinations { localhost; }; recursion yes; include "/etc/named.rfc1912.zones"; }; -- ACCEL Services, Inc.| Speciali...