To redirect all NXDOMAIN responses to
100.100.100.2 and
2001:ffff:ffff::100.100.100.2, one would
- configure the redirect zone like this:
+ configure a type redirect zone named ".",
+ with the zone file containing wildcard records
+ that point to the desired addresses:
+ <literal>"*. IN A 100.100.100.2"</literal>
+ and
+ <literal>"*. IN AAAA 2001:ffff:ffff::100.100.100.2"</literal>.
</para>
-<programlisting>
-zone "." {
- type redirect;
- file "redirect.db";
-};
-</programlisting>
- <para>
- ...with the zone file
- <filename>redirect.db</filename> containing the
- following:
- </para>
-<programlisting>
-$TTL 300
-@ IN SOA ns.example.net hostmaster.example.net 0 0 0 0 0
-@ IN NS ns.example.net
-;
-; NS records do not need address records in this zone as it is not in the
-; normal namespace.
-;
-*. IN A 100.100.100.2
-*. IN AAAA 2001:ffff:ffff::100.100.100.2
-</programlisting>
<para>
To redirect all Spanish names (under .ES) one
- would use entries like these:
+ would use similar entries but with the names
+ "*.ES." instead of "*.". To redirect all
+ commercial Spanish names (under COM.ES) one
+ would use wildcard entries called "*.COM.ES.".
</para>
-<programlisting>
-*.ES. IN A 100.100.100.3
-*.ES. IN AAAA 2001:ffff:ffff::100.100.100.3
-</programlisting>
- <para>
- And to redirect all commercial Spanish names
- (under COM.ES) one would use entries like these:
- </para>
-<programlisting>
-*.COM.ES. IN A 100.100.100.4
-*.COM.ES. IN AAAA 2001:ffff:ffff::100.100.100.4
-</programlisting>
<para>
Note that the redirect zone supports all
possible types; it is not limited to A and
- AAAA record.
+ AAAA records.
</para>
</entry>
</row>