1 ; An example domain table for the NSC
3 ; Hints how to find root servers
6 ; Various mandatory things required by RFC 1912, section 4.1
8 REVERSE(127.0.0, localhost)
10 ; Blackhole zones recommended by RFC 6303
11 BLACKHOLE(REV(0)) ; IPv4 reserved net
12 BLACKHOLE(REV(127)) ; IPv4 loopback net
13 BLACKHOLE(REV(169.254)) ; IPv4 link-local
14 BLACKHOLE(REV(192.0.2)) ; IPv4 test
15 BLACKHOLE(REV(198.51.100)) ; IPv4 test
16 BLACKHOLE(REV(203.0.113)) ; IPv4 test
17 BLACKHOLE(REV(255.255.255.255)) ; IPv4 broadcast
18 BLACKHOLE(REV(::1/128)) ; IPv6 loopback
19 BLACKHOLE(REV(::0/128)) ; IPv6 unspecified
20 BLACKHOLE(REV(fd00::/8)) ; IPv6 locally assigned
21 BLACKHOLE(REV(fe80::/12)) ; IPv6 link-local
22 BLACKHOLE(REV(fe90::/12))
23 BLACKHOLE(REV(fea0::/12))
24 BLACKHOLE(REV(feb0::/12))
25 BLACKHOLE(REV(2001:0db8::/32)) ; IPv6 example prefix
27 ; Blackhole zones for site-local addresses recommended by RFC 6303
29 nsc_forloop(`i', 16, 31, `BLACKHOLE(REV(172.i))')
30 BLACKHOLE(REV(192.168))
32 ; A pretty normal example domain (we act as a primary nameserver for it)
36 ; It also has a couple of sub-domains and one of them resides on another server
38 PRIMARY(a.example.com)
39 SECONDARY(b.example.com, 10.0.0.1)
41 ; Yet another subdomain residing on another server, but this time with
42 ; access restricted to the internal network. The closing quote after the
43 ; options has to be on a separate line, because semicolon is a comment character.
45 ZONE_OPTIONS(`allow-query { 127.0.0.0/8; 10.0.0.0/8; };
46 allow-recursion { 127.0.0.0/8; 10.0.0.0/8; };
47 allow-transfer { 127.0.0.0/8; 10.0.0.0/8; };
49 SECONDARY(priv.example.com, 10.10.10.1)
52 ; Here are reverse delegations for two networks. NSC automatically creates
53 ; the PTR records from A records in all mentioned zones. See cf/{0,1}.0.10.
55 REVERSE(10.0.0, example.com, a.example.com)
56 REVERSE(10.1.0, example.com, a.example.com, ip6.example.com)
58 ; You can even have reverse zones for larger networks
60 REVERSE(10.2, a.example.com)
62 ; Here are the examples of classless reverse delegation using subdomains
63 ; and PTR records as recommended by RFC 2317. We use the subdomain names
64 ; recommended by the RFC, however, this is not fixed anywhere and you can
65 ; use any names you like (or your ISP likes).
67 ; In the 10.1.0 network, we define a classless delegation (see cf/0.1.10),
68 ; but we also want to run a secondary server for the subdomain. As usually,
69 ; the REV macro is handy for constructing a reverse domain name.
71 SECONDARY(REV(10.1.0.128/25), 10.1.0.2)
73 ; And vice versa: we are delegated 10.3.0.64/26, so we want to create
74 ; the corresponding subdomain. The "/" in domain name gets automatically
75 ; translated to "@" when forming a file name, so you will find the corresponding
76 ; config file in cf/64@26.0.3.10.
78 REVERSE(10.3.0.64/26, a.example.com)
80 ; The final challenge: a subdomain with both IPv4 and IPv6 records
81 ; together with the corresponding reverse records (in IPv6 mode, all
82 ; networks are always accompanied by a netmask).
83 ; See cf/ip6.example.com and cf/4.3.2.1.0.c.e.f for details
85 PRIMARY(ip6.example.com)
86 REVERSE(fec0:1234::/32, ip6.example.com)
88 ; One more: a forward-only zone
90 FORWARDING(fwd.example.com, 10.0.0.1, 10.0.0.2)