1CSV2(5) MaraDNS reference CSV2(5)
2
6 csv2 - Description of the csv2 zone file that MaraDNS uses
7
9 The csv2 zone file format is MaraDNS' standard zone file format. This
10 zone file format uses any kind of whitespace (space, tab, and carriage
11 return), or the '|' character, to delimit fields.
12 Tilde delimitation
14 In newer MaraDNS releases, the tilde ('~') character is used to delimit
16 records in csv2 zone files; in order to maintain maximum compatibility
17 with older MaraDNS zone files, this feature is only enabled if a tilde
18 is placed between the first and second record. Otherwise, tildes are
19 not allowed in zone files (except in comments).
20 Most older MaraDNS csv2 zone files without the tilde character are
22 compatible with the updated csv2 parser, unless csv2_tilde_handling is
23 set to 3. All older MaraDNS csv2 zone files will parse in MaraDNS if
24 csv2_tilde_handling has a value of 0. Older MaraDNS releases also
25 supported the csv2_tilde_handling variable (as long as it had a value
26 of 0); this allowed the same configuration and zone files to be used in
27 older and newer MaraDNS releases.
28 Resource record format
30 This zone file format has records in the following form:
32 name [+ttl] [rtype] rdata ~
34 The name is the name of the record we will add, such as
36 "www.example.net.". This must be placed at the beginning of a line.
37 The rtype is the record type for the record, such as "A" (ipv4 IP
38 address), "MX" (mail exchanger), or "AAAA" (ipv6 IP address). The ttl
39 is how long other DNS servers should store this data in their memory
40 (in seconds); this field needs a '+' as its initial character. The
41 rdata is the actual data for this record; the format for the rdata is
42 type-specific.
43 Anything in square brackets is an optional field. If the ttl is not
45 specified, the ttl is set to the default ttl value (see "Default TTL"
46 below). If the rtype is not specified, it is set to be an "A" (ipv4
47 address) record.
48 The zone file supports comments; comments are specified by having a '#'
50 anywhere between fields or records; when a '#' is seen, the csv2 parser
51 ignores any character it sees (with the exception of the '{', which is
52 not allowed in comments) until a newline. A '#' can usually be placed
53 inside a field, and indicates the end of a field when placed there.
54 A '{' character can never be placed in a comment. A '~' character is
56 always allowed in a comment, and has no special meaning when placed in
57 a comment.
58 The following record types are supported; a description of the record
60 data format accommodates the record type:
61 A
63 An A record stores an ipv4 address. This is the default record type
65 should the record type not be specified. The record type has one field
66 in it: the IP for the record. Examples:
67 a.example.net. 10.11.12.13 ~
69 b.example.net. A 10.11.12.14 ~
70 c.example.net. +64000 A 10.11.12.15 ~
71 PTR
73 A PTR record stores the name for a given ipv4 or ipv6 address, and is
75 used for reverse DNS lookups. This record type has one field in it: The
76 name for the record in question. Examples:
77 13.12.11.10.in-addr.arpa. PTR a.example.net. ~
79 14.12.11.10.in-addr.arpa. PTR b.example.net. ~
80 15.12.11.10.in-addr.arpa. +64000 PTR c.example.net. ~
81 MX
83 A MX record stores a mail exchange record, and is used for mail
85 delivery. This record type has two fields in it: The priority (or
86 "preference" in traditional DNS parlance) of the MX record (lower
87 numbers get higher priority), and the name of the mail exchanger.
88 Example of mail for example.net being mailed to mail.example.net, which
89 has the IP "10.11.12.16":
90 example.net. MX 10 mail.example.net. ~
92 mail.example.net. 10.11.12.16 ~
93 AAAA
95 An AAAA record stores the ipv6 address for a given name. The IP is in
97 standard ipv6 "colon delimited" format: eight 16-bit hexadecimal
98 numbers are separated by colons. Two colons together indicate multiple
99 streams of all-zero hex numbers. This record has only one field, the v6
100 IP. Example:
101 a.example.net. AAAA fd4d:6172:6144:4e53:ffe::f ~
103 SRV
105 An SRV record stores a "service" definition. This record has four
107 fields: Priority, weight, port, and target. For more information,
108 please refer to RFC 2782. Example:
109 _http._tcp.% SRV 0 0 80 a.% ~
111 NAPTR
113 A NAPTR record is described in RFC 2915. Example:
115 www.example.com. NAPTR 100 100 's';'http+I2R';'' _http._tcp.example.com. ~
117 Note the semicolons. Because of a bug in MaraDNS 1.4.03 and earlier
119 releases, NAPTR records will not parse unless a ~ is not used to
120 separate records; a patch to fix this bug is available here.
121 NS
123 An NS record specifies the name servers for a given zone. If the name
125 servers are not delegation name servers (in other words, if the name
126 servers are the authoritative name servers for the zone), they need to
127 be at the beginning of the zone, either as the first records in the
128 zone, or right after the SOA record. The NS records are optional; if
129 not present, MaraDNS will make an educated guess of that NS records
130 should be there, based on the IPs the MaraDNS process is bound to. This
131 record has one field: The name of the name server machine. Example:
132 example.net. NS ns1.example.net. ~
134 example.net. NS ns2.example.net. ~
135 SOA
137 An SOA record stores the start of authority for a given zone file.
139 This record is optional in a CSV2 zone file; should the record not be
140 in the zone file, MaraDNS will synthesize an appropriate SOA record.
141 This record can only exist once in a zone file: As the first record of
142 the zone file. This record has seven fields: The name of the zone, the
143 email address of the person responsible for the zone, and five numeric
144 fields (serial, refresh, retry, expire, and minimum). Note that the
145 SOA minimum does not affect other TTLs in MaraDNS. Example:
146 x.org. SOA x.org. email@x.org. 1 7200 3600 604800 1800 ~
148 If there is a '.' (dot) character in the part of the email address
150 before the '@', it needs to be escaped thusly:
151 x.org. SOA x.org. john\.doe@x.org. 1 7200 3600 604800 1800 ~
153 Note that the csv2 parser will not allow more than one dot in a row;
155 'john\.\.doe@x.org' will cause a parse error. In addition, the dot
156 character must be escaped with a backslash.
157 The serial numeric field may be replaced by the string '/serial'; this
159 string tells the CSV2 zone parser to synthesize a serial number for the
160 zone based on the timestamp for the zone file. This allows one to have
161 the serial number be automatically updated whenever the zone file is
162 edited. Here is how this special field looks in a SOA record:
163 x.org. SOA x.org. email@x.org. /serial 7200 3600 604800 1800 ~
165 The '/serial' string is case-sensitive; only '/serial' in all lower
167 case will parse.
168 TXT
170 A TXT record stores arbitrary text and/or binary data for a given host
172 name. This record has one field: The text data for the record.
173 A basic text record can be stored by placing ASCII data between two
175 single quotes, as follows:
176 example.com. TXT 'This is an example text field' ~
178 Any binary data can be specified; see the csv2_txt(5) manual page for
180 full details.
181 If tildes are used to separate records, a TXT record can not contain a
183 literal '|' (pipe) character, a '#' literal, a '~' literal, nor any
184 ASCII control literal; these characters can be added to a TXT record
185 via the use of escape sequences; read the csv2_txt man page for
186 details.
187 SPF
189 A SPF record is, with the exception of the numeric rtype, identical to
191 a TXT record. SPF records are designed to make it more difficult to
192 forge email. Here is one example SPF record:
193 example.com. SPF 'v=spf1 +mx a:colo.example.com/28 -all'
195 Use '\x7e' to put a tilde ("~" character) in a SPF record:
197 example.com. SPF 'v=spf1 +mx a:colo.example.com/28 '\x7e'all'
199 More information about SPF records can be found in RFC4408, or by
201 performing a web search for 'sender policy framework'.
202 RAW
204 The RAW record is a special meta-record that allows any otherwise
206 unsupported record type to be stored in a csv2 zone file. The syntax
207 is:
208 RAW [numeric rtype] [data] ~
210 The numeric rtype is a decimal number.
212 The data field can, among other thing, have backslashed hex sequences
214 outside of quotes, concatenated by ASCII data inside quotes, such as
215 the following example:
216 example.com. RAW 40 \x10\x01\x02'Kitchen sink'\x40' data' ~
218 The above example is a "Kitchen Sink" RR with a "meaning" of 16, a
220 "coding" of 1, a "subcoding" of 2, and a data string of "Kitchen sink@
221 data" (since hex code 40 corresponds to a @ in ASCII). Note that
222 unquoted hex sequences are concatenated with quoted ASCII data, and
223 that spaces are only inside quoted data.
224 The format for a data field in a RAW record is almost identical to the
226 format for a TXT data field. Both formats are described in full in the
227 csv2_txt(5) manual page.
228 FQDN4
230 The FQDN4 (short for "Fully Qualified Domain Name for IPv4") record is
232 a special form of the "A" record (see above) that instructs MaraDNS to
233 automatically create the corresponding PTR record. For example, the
234 following is one way of setting up the reverse DNS lookup for
235 x.example.net:
236 x.example.net. A 10.3.28.79 ~
238 79.28.3.10.in-addr.arpa. PTR x.example.net. ~
239 But the above two lines in a zone file can also be represented thusly:
241 x.example.net. FQDN4 10.3.28.79 ~
243 Note that the csv2 parser does not bother to check that any given IP
245 only has a single FQDN4 record; it is up to the DNS administrator to
246 ensure that a given IP has only one FQDN4 record. In the case of there
247 being multiple FQDN4 records with the same IP, MaraDNS will have
248 multiple entries in the corresponding PTR record, which is usually not
249 the desired behavior.
250 FQDN4 records are not permitted in a csv2_default_zonefile. If you do
252 not know what a csv2_default_zonefile is, you do not have to worry
253 about this limitation.
254 FQDN6
256 The FQDN6 (short for "Fully Qualified Domain Name for IPv6") record is
258 the ipv6 form for the FQDN4 record. Like the FQDN4 record, this record
259 creates both a "forward" and "reverse" DNS record for a given host
260 name. For example, onoe may have:
261 x.example.net. AAAA fd4d:6172:6144:4e53::b:c:d ~
263 d.0.0.0.c.0.0.0.b.0.0.0.0.0.0.0.3.5.e.4.4.4.1.6.2.7.1.6.d.4.d.f PTR
264 x.example.net. ~
265 But the above two lines in a zone file can also be represented thusly:
267 x.example.net. FQDN6 fd4d:6172:6144:4e53::b:c:d ~
269 Like FQDN4 records, it is the DNS administrator's duty to make sure
271 only a single IP has a FQDN6 record.
272 FQDN6 records are, like FQDN4 records, not permitted in a
274 csv2_default_zonefile. If you do not know what a csv2_default_zonefile
275 is, you do not have to worry about this limitation.
276 FQDN6 records were implemented by Jean-Jacques Sarton.
278 CNAME
280 A CNAME record is a pointer to another host name. The CNAME record, in
282 MaraDNS, affects any record type not already specified for a given host
283 name. While MaraDNS allows CNAME and non-CNAME records to share the
284 same host name, this is considered bad practice and is not compatible
285 with some other DNS servers.
286 CNAME records are not permitted in a csv2_default_zonefile. If you do
288 not know what a csv2_default_zonefile is, this fact is of no relevance.
289
291 The following resource records are mainly of historical interest, or
292 are not commonly used.
293 HINFO
295 An HINFO record is a description of the CPU (processor) and OS that a
297 given host is using. The format for this record is identical to a TXT
298 record, except that the field must have precisely two chunks.
299 The first chunk of a HINFO record is the CPU the host is running; the
301 second chunk is the OS the host is running.
302 Example:
304 example.com. HINFO 'Intel Pentium III';'CentOS Linux 3.7' ~
306 This resource record is not actively used--the IANA has a list of CPUs
308 and OSes that this record is supposed to have. However, this list has
309 not been updated since 2002.
310 WKS
312 WKS records are historical records which have been superseded by SRV
314 records. The format of the record is an IP, followed by a protocol
315 number (6 means TCP), followed by a list of ports that a given server
316 has available for services.
317 For example, to advertise that example.net has the IP 10.1.2.3, and has
319 a SSH, HTTP (web), and NNTP server:
320 example.net. WKS 10.1.2.3 6 22,80,119 ~
322 MaraDNS only allows up to 10 different port numbers in a WKS record,
324 and requires that the listed port numbers are not be higher than 1023.
325 MD and MF
327 MD and MF records are RR types that existed before MX records, and were
329 made obsolete by MX records. RFC1035 says that a DNS server can either
330 reject these records or convert these records in to MX records. BIND
331 rejects these records; MaraDNS converts them.
332 Example:
334 example.net. MD a.example.net. ~
336 example.net. MF b.example.net. ~
337 Is equivalent to:
339 example.net. MX 0 a.example.net. ~
341 example.net. MX 10 b.example.net. ~
342 MB, MG, MINFO, and MR
344 In the late 1980s, an alternative to MX records was proposed. This
346 alternative utilized MB, MG, MINFO, and MR records. This alternative
347 failed to gather popularity. However, these records were codified in
348 RFC1035, and are supported by MaraDNS. Here is what the records look
349 like:
350 example.net. MB mail.example.net. ~
352 example.net. MG mg@example.net. ~
353 example.net. MINFO rm@example.net. re@example.net. ~
354 example.net. MR mr@example.net. ~
355 More information about these records can be found in RFC1035.
357 AFSDB, RP, X25, ISDN, and RT
359 AFSDB, RP, X25, ISDN, and RT are resource records which were proposed
361 in RFC1183. None of these resource records are widely used.
362 With the exception of the ISDN record, the format of these records is
364 identical to the examples in RFC1183. The format of the ISDN record is
365 identical unless the record has a subaddress (SA). If an ISDN record
366 has a subaddress, it is separated from the ISDN-address by a ';'
367 instead of whitespace.
368 If used, here is how the records would look in a csv2 zone file:
370 example.net. AFSDB 1 afsdb.example.net. ~
372 example.net. RP rp@example.net. rp.example.net. ~
373 example.net. RP rp2@example.net. . ~
374 example.net. X25 311061700956 ~
375 example.net. ISDN 150862028003217 ~
376 example.net. ISDN 150862028003217;004 ~
377 example.net. RT 10 relay.example.net. ~
378 NSAP and NSAP-PTR
380 NSAP and NSAP-PTR records were proposed in RFC1706. A NSAP record is a
382 hexadecimal number preceded by the string "0x" and with optional dots
383 between bytes. This hexadecimal number is converted in to a binary
384 number by MaraDNS. A NSAP-PTR record is identical to a PTR record, but
385 has a different RTYPE.
386 More information about these records can be obtained from RFC1706.
388 If used, here is how the records would look in a csv2 zone file:
390 example.net. NSAP 0x47.0005.80.005a00.0000.0001.e133.ffffff000162.00 ~
392 example.net. NSAP-PTR nsap.example.net. ~
393 PX
395 The PX RR is an obscure RR described in RFC2163. A PX record looks like
397 this in a CSV2 zone file:
398 example.net. PX 15 px1.example.net. px2.example.net. ~
400 GPOS
402 An GPOS record is a description of the location of a given server. The
404 format for this record is identical to a TXT record, except that the
405 field must have precisely three chunks.
406 The first chunk of a GPOS record is the longitude; the second chunk is
408 the latitude; the third chunk is the altitude (in meters).
409 Example:
411 example.net. GPOS '-98.6502';'19.283';'2134' ~
413 More information about this record can be found in RFC1712.
415 This resource record is not actively used; for the relatively few
417 people who encode their position in DNS, the LOC record is far more
418 common.
419 LOC
421 The LOC resource record is an uncommonly used resource record that
423 describes the position of a given server. LOC records are described in
424 RFC1876.
425 Note that MaraDNS' LOC parser assumes that the altitude, size,
427 horizontal, and vertical precision numbers are always expressed in
428 meters. Also note that that sub-meter values for size, horizontal, and
429 vertical precision are not allowed. Additionally, the altitude can not
430 be greater than 21374836.47 meters.
431 Example:
433 example.net. LOC 19 31 2.123 N 98 3 4 W 2000m 2m 4m 567m ~
435
438 In addition to being able to have resource records and comments, csv2
439 zone files can also have special slash commands. These slash commands,
440 with the exception of the '/serial' slash command (see "SOA" above),
441 can only be placed where the name for a record would be placed. Like
442 resource records, a tilde is to be placed after the slash command. Note
443 also that slash commands are case-sensitive, and the command in
444 question must be in all-lower-case.
445 These commands are as follows:
447 Default TTL
449 The default TTL is the TTL for a resource record without a TTL
451 specified. This can be changed with the '/ttl' slash command. This
452 command takes only a single argument: The time, in seconds, for the new
453 default TTL. The '/ttl' slash command only affects the TTL of records
454 that follow the command. A zone file can have multiple '/ttl' slash
455 commands.
456 The default TTL is 86400 seconds (one day) until changed by the '/ttl'
458 slash command.
459 In the following example, a.ttl.example.com will have a TTL of 86400
461 seconds (as long as the zone file with this record has not previously
462 used the '/ttl' slash command), b.ttl.example.com and d.ttl.example.com
463 will have a TTL of 3600 seconds, c.ttl.example.com will have a TTL of
464 9600 seconds, and e.ttl.example.com will have a TTL of 7200 seconds:
465 a.ttl.example.com. 10.0.0.1 ~
467 /ttl 3600 ~
468 b.ttl.example.com. 10.0.0.2 ~
469 c.ttl.example.com. +9600 10.0.0.3 ~
470 d.ttl.example.com. 10.0.0.4 ~
471 /ttl 7200 ~
472 e.ttl.example.com. 10.0.0.5 ~
473 Origin
475 It is possible to change the host name suffix that is used to
477 substitute the percent in a csv2 zone file. This suffix is called, for
478 historical and compatibility reasons, "origin". This is done as the
479 slash command '/origin', taking the new origin as the one argument to
480 this function. Note that changing the origin does not change the
481 domain suffix used to determine whether a given domain name is
482 authoritative.
483 Here is one example usage of the '/origin' slash command:
485 /origin example.com. ~
487 www.% 10.1.0.1 ~
488 % MX 10 mail.% ~
489 mail.% 10.1.0.2 ~
490 /origin example.org. ~
491 www.% 10.2.0.1 ~
492 % MX 10 mail.% ~
493 mail.% 10.2.0.2 ~
494 Which is equivalent to:
496 www.example.com. 10.1.0.1 ~
498 example.com. MX 10 mail.example.com. ~
499 mail.example.com. 10.1.0.2 ~
500 www.example.org. 10.2.0.1 ~
501 example.org. MX 10 mail.example.org. ~
502 mail.example.org. 10.2.0.2 ~
503 It is also possible to make the current origin be part of the new
505 origin:
506 /origin example.com. ~
508 % 10.3.2.1 ~ # example.com now has IP 10.3.2.1
509 /origin mail.% ~
510 % 10.3.2.2 ~ # mail.example.com now has IP 10.3.2.2
511 Opush and Opop
513 The '/opush' and '/opop' slash commands use a stack to remember and
515 later recall values for the origin (see origin above). The '/opush'
516 command is used just like the '/origin' command; however, the current
517 origin is placed on a stack instead of discarded. The '/opop' command
518 removes ("pops") the top element from this stack and makes the element
519 the origin.
520 For example:
522 /origin example.com. ~
524 /opush mail.% ~ # origin is now mail.example.com; example.com is on stack
525 a.% 10.4.0.1 ~ # a.mail.example.com has IP 10.4.0.1
526 /opush web.example.com. ~ # mail.example.com and example.com are on stack
527 a.% 10.5.0.1 ~ # a.web.example.com has IP 10.5.0.1
528 b.% 10.5.0.2 ~ # b.web.example.com has IP 10.5.0.2
529 /opop ~ # origin is now mail.example.com again
530 b.% 10.4.0.2 ~ # b.mail.example.com has IP 10.4.0.2
531 /opop ~ # origin is now example.com
532 % MX 10 a.mail.% ~ # example.com. MX 10 a.mail.example.com.
533 % MX 20 b.mail.% ~ # example.com. MX 20 b.mail.example.com.
534 The opush/opop stack can have up to seven elements on it.
536 Read
538 The '/read' slash commands allows one to have the contents of another
540 file in a zone. The '/read' command takes a single argument: A filename
541 that one wishes to read. The filename is only allowed to have letters,
542 numbers, the '-' character, the '_' character, and the '.' character in
543 it.
544 The file needs to be in the same directory as the zone file. The file
546 will be read with the same privileges as the zone file; content in the
547 file should come from a trusted source or be controlled by the system
548 administrator.
549 Let us suppose that we have the following in a zone file:
551 mail.foo.example.com. 10.3.2.1 ~
553 /read foo ~
554 foo.example.com. MX 10 mail.foo.example.com. ~
555 And a file foo with the following contents:
557 foo.example.com. 10.1.2.3 ~
559 foo.example.com. TXT 'Foomatic!' ~
560 Then foo.example.com will have an A record with the value 10.1.2.3, a
562 TXT value of 'Foomatic!', and a MX record with priority 10 pointing to
563 mail.foo.example.com. mail.foo.example.com will have the IP 10.3.2.1.
564 Note that no pre-processing nor post-processing of the origin is done
566 by the '/read' command; should the file read change the origin, this
567 changed value will affect any records after the '/read' command. For
568 example, let us suppose db.example.com looks like this:
569 /origin foo.example.com. ~
571 % TXT 'Foomatic!' ~
572 /read foo ~
573 % MX 10 mail.foo.example.com. ~
574 And the file foo looks like this:
576 % 10.1.2.3 ~
578 /origin mail.% ~
579 % 10.3.2.1 ~
580 Then the following records will be created:
582 foo.example.com. TXT 'Foomatic!' ~
584 foo.example.com. A 10.1.2.3 ~
585 mail.foo.example.com. A 10.3.2.1 ~
586 mail.foo.example.com. MX 10 mail.foo.example.com. ~
587 To have something that works like '$INCLUDE filename' in a RFC1035
589 master file, do the following:
590 /opush % ~
592 /read filename ~
593 /opop ~
594 Or, for that matter, the equivalent of '$INCLUDE filename neworigin':
596 /opush neworigin. ~
598 /read filename ~
599 /opop ~
600
603 # This is an example csv2 zone file
604 # First of all, csv2 zone files do not need an SOA record; however, if
606 # one is provided, we will make it the SOA record for our zone
607 # The SOA record needs to be the first record in the zone if provided
608 # This is a commented out record and disabled.
609 #% SOA % email@% 1 7200 3600 604800 1800 ~
611 # Second of all, csv2 zone files do not need authoritative NS records.
613 # If they aren't there, MaraDNS will synthesize them, based on the IP
614 # addresses MaraDNS is bound to. (She's pretty smart about this; if
615 # Mara is bound to both public and private IPs, only the public IPs will
616 # be synthesized as NS records)
617 #% NS a.% ~
620 #% NS b.% ~
621 # Here are some A (ipv4 address) records; since this is the most
623 # common field, the zone file format allows a compact representation
624 # of it.
625 a.example.net. 10.10.10.10 ~
626 # Here, you can see that a single name, "b.example.net." has multiple IPs
627 # This can be used as a primitive form of load balancing; MaraDNS will
628 # rotate the IPs so that first IP seen by a DNS client changes every time
629 # a query for "b.example.net." is made
630 b.example.net. 10.10.10.11 ~
631 b.example.net. 10.10.10.12 ~
632 # We can have the label in either case; it makes no difference
634 Z.EXAMPLE.NET. 10.2.3.4 ~
635 Y.EXAMPLE.net. 10.3.4.5 ~
636 # We can use the percent shortcut. When the percent shortcut is present,
638 # it indicates that the name in question should terminate with the name
639 # of the zone we are processing.
640 percent.% a 10.9.8.7 ~
641 # And we can have star records
643 #*.example.net. A 10.11.12.13 ~
644 # We can have a ttl in a record; however the ttl needs a '+' before it:
646 # Note that the ttl has to be in seconds, and is before the RTYPE
647 d.example.net. +86400 A 10.11.12.13 ~
648 f.example.net. # As you can see, records can span multiple lines
650 A 10.2.19.83 ~
651 # This allows well-commented records, like this:
653 c.example.net. # Our C class machine
654 +86400 # This record is stored for one day
655 A # A record
656 10.1.1.1 # Where we are
657 ~ # End of record
658 # We can even have something similar to csv1 if we want...
660 e.example.net.|+86400|a|10.2.3.4|~
661 h.example.net.|a|10.9.8.7|~
662 # Here, we see we can specify the ttl but not the rtype if desired
663 g.example.net.|+86400|10.11.9.8|~
664 # Here is a MX record
666 % mx 10 mail.% ~
667 mail.% +86400 IN A 10.22.23.24 ~
668 # We even have a bit of ipv6 support
670 a.example.net. aaaa fd4d:6172:6144:4e53:1:2:3::4:f ~
671 # Not to mention support for SRV records
673 _http._tcp.% srv 0 0 80 a.% ~
674 # TXT records, naturally
676 example.net. txt 'This is some text' ~
677 # Starting with MaraDNS 1.2.08, there is also support for SPF records,
679 # which are identical to TXT records. See RFC4408 for more details.
680 example.net. spf 'v=spf1 +mx a:colo.example.com/28 -all' ~
681
687 THIS SOFTWARE IS PROVIDED BY THE AUTHORS ''AS IS'' AND ANY EXPRESS OR
688 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
689 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
690 DISCLAIMED. IN NO EVENT SHALL THE AUTHORS OR CONTRIBUTORS BE LIABLE FOR
691 ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
692 DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
693 OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
694 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
695 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
696 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
697 POSSIBILITY OF SUCH DAMAGE.
698
700 Sam Trenholme http://www.samiam.org/
701MARADNS January 2007 CSV2(5)