Red Hat Enterprise Linux 5 Administration Unleashed

Configuring BIND 345Configuring ViewsOn a BIND server, views can be created to customize the data sent to different requestersbased on the source and destination IP addresses. Most of the global option statementscan also be used inside a view to override the default value or the value set as a globaloption. They have the following syntax:view {match-clients { } ;match-destinations { } ;match-recursive-only ;};The must be unique per view and should be a short, descriptive word describingthe view specifications. The is optional and defaults to IN.Use the match-clients clause to define the source address to match. Use the matchdestinationsclause to define the destination address of the request. If the source addressis not specified, requests from any source match. If the destination address is not specified,requests to be sent to any address match.The order in which views are listed in named.conf matters. The first view that matches thesource and/or destination addresses of the server requesting the data is used to format theresponse. So, view statements should go from the most restrictive to the least restrictive. Ifyou want to declare a view statement without a match-clients or match-destinationsstatement as a “catch-all” for requesters that don’t match any of the other statements, itshould be the last view statement in named.conf, or the other view statements will beignored because all requests will match the “catch-all” statement.16The keys statement allows clients a way to select the view. If the match-recursive-onlystatement is set to yes, only recursive requests match. If any views are defined, all zonestatements must be inside view statements. Zones defined inside views can only beaccessed by clients that match the view specifications.Configuring ZonesA zone statement is used to define a zone and its properties. Some global options apply tozones unless they are overridden inside the zone statement. Zone files are written to the/var/named/ directory.The statements have the following syntax:zone {type };The must be unique and must be the domain name for the zone such asexample.com or host.example.com. It is used to complete hostnames that are not FQDNs.