What you have is a (new to BIND 9) configuration for a cacheing-only local nameserver. This configuration will only respond to queries from "localhost" and for "localhost", because you have nearly all your config info specified within a view
. This may in fact be what you want, but unless the hostname of your RHEL 5 box is "localhost", maybe not. The most troublesome of the substatements in your view
specification seems to be
This substatement says that the view only applies to queries for the address of "localhost". This is almost certainly not what you want. I would recommend removing (or commenting out) this line and seeing how things stand once you restart named.
Perhaps you can tell us a little more about what does and does not work when named
is running; at the same time, if there are any complaints in the logfile from named
, please post them as well. I think the default for error messages (since you have nothing for them in your logging section) is syslog, which will put them into /var/log/messages
The things to check are:
1. Using dig
, can your box resolve "localhost" to 127.0.0.1 ?
2. Can it do the reverse (given 127.0.0.1, does the name come back "localhost") ?
3. Can it reach a root server (the names and addresses are listed in /var/named/chroot/var/named/named.ca
4. Can it reach a well-known Internet site (eg www.google.com
After that, let us know what else does not work. As things are configured now, no other machine on your local net will be able to use the cacheing nameserver. You can change that by creating an access control list
, specifying addresses or address ranges, and then substituting that acl name for "localhost" in two places: in allow-query
, and in match-clients