whats the frequency of the letter a in:
q: set up reverse delegation for documentation address in rfc 5737? i am using core to develop some network emulations to teach some network concepts. one of those concepts is the correct setup of


*

*a recursive dns server for local clients;

*an authoritative dns server for a domain; and

*the reverse delegation for ipv4 and ipv6 prefixes.


considering the documentation nature of the emulation, i have being using test-net, test-net2 and test-net3 prefixes described in rfc5737. i also found out about rfc6303, which was written by a member of isc (binds developers), which states:

the following zones correspond to those address ranges from [rfc5735]
     and [rfc5737] that are not expected to appear as source or
     destination addresses on the public internet; as such, there are no
     globally unique names associated with the addresses in these ranges.

is there any way to configure bind9 to act as a recursive dns server that bypasses the behavior established on rfc6303 (i.e., make recursion beginning with the root server, even if it belongs to one of the test-nets address range)?

a: check the bind 9 administrators reference manual for your version.  you want to look into the commands to enable/disable empty-zones.  


*

*enable-empty-zones allows you to turn them all on or off

*disable-empty-zones allows you to disable specified ones individually


the default setting for empty zones (enabled or not) depends on what series of bind you are running; it changed relatively recently (i cant recall for certain but i think in 9.7 or 9.8.) 
i am assuming that you are interested in using this within your classroom simulated environment or in an isolated network where you plan to operate your own dns root.  please use this responsibly -- dont deluge the real-world root servers with requests for rfc 1918 zones, etc.

user
In the text, there are ninety-three "a"s.
assistant