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 (bind's 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)?