Bug 437569

Description of problem:
Misconfigurations in named.conf configuration template

Version-Release number of selected component (if applicable):
Seen with version 9.5.0 on Fedora 7 and 9.3.3 on CentOS 5.1 (so is probably in
other RH Linux versions as well).

How reproducible:

Steps to Reproduce:
1. create a named configuration based on the template named.conf in
/usr/share/doc/bind-9.x.x/sample/etc/named.conf
2. do a query from an outside IP address, e.g. dig @nameserver host.domain

Actual results:
query refused

Expected results:
answer

Additional info:
I think the "match-clients" and "match-destinations" were misunderstood when
creating this template. These are matched against the source and destination
address, respectively, of the query.

They now read:
view "localhost_resolver" {
  match-clients { localhost; };
  match-destinations { localhost; };
  ...
  }
view "internal" {
  match-clients { localnets; };
  match-destinations { localnets; };
  ...
  }
view "external" {
  match-clients { !localnets; !localhost; };
  match-destinations { !localnets; !localhost; };
  ...
  }

Causing a refusal from an external client since there will never be a match.

I think these statements should read (works for me to get this solved):
view "localhost_resolver" {
  match-clients { localhost; };
  match-destinations { localhost; };
  ...
  }
view "internal" {
  match-clients { localnets; };
  match-destinations { localhost; };
  ...
  }
view "external" {
  match-clients { !localnets; !localhost; any; };
  match-destinations { localhost; };
  ...
  }