4
4
.\" Process this file with the following
5
5
.\" nroff -man -Tutf8 maradns.8 | tr '\020' ' '
7
.\" Last updated Thu Mar 22 01:31:36 2007
7
.\" Last updated Fri Jan 8 10:07:48 2010
9
9
.TH CSV2 5 "January 2007" MARADNS "MaraDNS reference"
10
10
.\" We don't want hyphenation (it's too ugly)
25
25
csv2 - Description of the csv2 zone file that MaraDNS uses
28
The csv2 zone file format is the zone file format introduced in MaraDNS
28
The csv2 zone file format is MaraDNS\(aq standard zone file format.
30
29
This zone file format uses any kind of whitespace (space, tab, and
32
return), or the \(aq|\(aq character, to deliminate fields.
31
return), or the \(aq|\(aq character, to delimit fields.
35
\fBTilde delimination\fR
37
In MaraDNS 1.3, the tilde (\(aq~\(aq) character is used to deliminate
39
in csv2 zone files; in order to maintain maximum compatibility with
40
MaraDNS 1.2 zone files, this feature is only enabled if a tilde is
41
placed between the first and second record. Otherwise, tildes are
42
not allowed in zone files (except in comments).
44
Most MaraDNS 1.2 csv2 zone files without the tilde character are
45
compatible with the 1.3 csv2 parser, unless csv2_tilde_handling
46
is set to 3. All MaraDNS 1.2 csv2 zone files will parse in MaraDNS 1.3
47
if csv2_tilde_handling has a value of 0. MaraDNS 1.2, starting with
48
1.2.12.04, also supports the csv2_tilde_handling variable (as long as
50
has a value of 0); this allows the same configuration and zone files to
51
be used in both MaraDNS 1.2 and MaraDNS 1.3.
34
\fBTilde delimitation\fR
36
In newer MaraDNS releases, the tilde (\(aq~\(aq) character is used to
38
records in csv2 zone files; in order to maintain maximum compatibility
39
with older MaraDNS zone files, this feature is only enabled if a tilde
41
placed between the first and second record. Otherwise, tildes are not
42
allowed in zone files (except in comments).
44
Most older MaraDNS csv2 zone files without the tilde character are
45
compatible with the updated csv2 parser, unless csv2_tilde_handling
46
is set to 3. All older MaraDNS csv2 zone files will parse in MaraDNS
47
if csv2_tilde_handling has a value of 0. Older MaraDNS releases
48
also supported the csv2_tilde_handling variable (as long as it
49
had a value of 0); this allowed the same configuration and zone files
51
be used in older and newer MaraDNS releases.
54
54
\fBResource record format\fR
174
174
An NS record specifies the name servers for a given zone. If the name
175
servers are not delegation name servers (in other words, if the the
175
servers are not delegation name servers (in other words, if the name
177
176
servers are the authoritative name servers for the zone), they need to
179
178
at the beginning of the zone, either as the first records in the zone,
326
325
about this limitation.
330
The FQDN6 (short for "Fully Qualified Domain Name for IPv6") record is
331
the ipv6 form for the FQDN4 record. Like the FQDN4 record, this
332
record creates both a "forward" and "reverse" DNS record for a given
333
host name. For example, onoe may have:
336
x.example.net. AAAA 3ffe:ffff:ffe:501:ffff::b:c:d ~
337
d.0.0.0.c.0.0.0.b.0.0.0.f.f.f.f.1.0.5.0.e.f.f.0.f.f.f.f.e.f.f.3 PTR
341
But the above two lines in a zone file can also be represented thusly:
344
x.example.net. FQDN6 3ffe:ffff:ffe:501:ffff::b:c:d ~
347
Like FQDN4 records, it is the DNS administrator\(aqs duty to make sure
348
only a single IP has a FQDN6 record.
350
FQDN6 records are, like FQDN6 records, not permitted in a
351
csv2_default_zonefile. If you do not know what a csv2_default_zonefile
352
is, you do not have to worry about this limitation.
354
FQDN6 records were implemented by Jean-Jacques Sarto.
331
359
A CNAME record is a pointer to another host name. The CNAME record, in
453
481
\fBNSAP and NSAP-PTR\fR
455
483
NSAP and NSAP-PTR records were proposed in RFC1706. A NSAP record is
456
a hexadecimal number preceeded by the string "0x" and with optional
484
a hexadecimal number preceded by the string "0x" and with optional dots
458
485
between bytes. This hexadecimal number is converted in to a binary
460
by MaraDNS. A NSAP-PTR record is idenical to a PTR record, but has a
487
by MaraDNS. A NSAP-PTR record is identical to a PTR record, but has a
463
490
More information about these records can be obtained from RFC1706.
798
825
10.1.1.1 # Where we are
799
826
~ # End of record
801
# We can even have something similiar to csv1 if we want...
828
# We can even have something similar to csv1 if we want...
802
829
e.example.net.|+86400|a|10.2.3.4|~
803
830
h.example.net.|a|10.9.8.7|~
804
831
# Here, we see we can specify the ttl but not the rtype if desired