On Thu, Mar 05, 2009 at 02:06:18PM +0100, squid proxy <squidcac...@gmail.com> wrote a message of 13 lines which said:
> Howto create a stub zone instead of slave zone on BIND 9.3.4-P1.1? Read the documentation ? <https://www.isc.org/software/bind/documentation/arm95> zone zone_name [class] { type stub; [ allow-query { address_match_list }; ] [ allow-query-on { address_match_list }; ] ... }; > What are differences between slave and stub zone? Read the documentation ? <https://www.isc.org/software/bind/documentation/arm95> A stub zone is similar to a slave zone, except that it replicates only the NS records of a master zone instead of the entire zone. Stub zones are not a standard part of the DNS; they are a feature specific to the BIND implementation. Stub zones can be used to eliminate the need for glue NS record in a parent zone at the expense of maintaining a stub zone entry and a set of name server addresses in named.conf. This usage is not recommended for new configurations, and BIND 9 supports it only in a limited way. In BIND 4/8, zone transfers of a parent zone included the NS records from stub children of that zone. This meant that, in some cases, users could get away with configuring child stubs only in the master server for the parent zone. BIND 9 never mixes together zone data from different zones in this way. Therefore, if a BIND 9 master serving a parent zone has child stub zones configured, all the slave servers for the parent zone also need to have the same child stub zones configured. Stub zones can also be used as a way of forcing the resolution of a given domain to use a particular set of authoritative servers. For example, the caching name servers on a private network using RFC1918 addressing may be configured with stub zones for 10.in-addr.arpa to use a set of internal name servers as the authoritative servers for that domain. _______________________________________________ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
