Commit 521a519d authored by Daniel Salzman's avatar Daniel Salzman

doc: unify RFC links use

parent b1345cc8
......@@ -198,7 +198,7 @@ server:
.SS identity
.sp
An identity of the server returned in the response to the query for TXT
record \fBid.server.\fP or \fBhostname.bind.\fP in the CHAOS class (see RFC 4892).
record \fBid.server.\fP or \fBhostname.bind.\fP in the CHAOS class (\fI\%RFC 4892\fP).
Set empty value to disable.
.sp
\fIDefault:\fP FQDN hostname
......@@ -206,12 +206,12 @@ Set empty value to disable.
.sp
A version of the server software returned in the response to the query
for TXT record \fBversion.server.\fP or \fBversion.bind.\fP in the CHAOS
class (see RFC 4892). Set empty value to disable.
class (\fI\%RFC 4892\fP). Set empty value to disable.
.sp
\fIDefault:\fP server version
.SS nsid
.sp
A DNS name server identifier (see RFC 5001). Set empty value to disable.
A DNS name server identifier (\fI\%RFC 5001\fP). Set empty value to disable.
.sp
\fIDefault:\fP FQDN hostname
.SS rundir
......@@ -1045,13 +1045,13 @@ logged only.
Mandatory checks:
.INDENT 0.0
.IP \(bu 2
SOA record missing in the zone (RFC 1034)
SOA record missing in the zone (\fI\%RFC 1034\fP)
.IP \(bu 2
An extra record together with CNAME record except for RRSIG and DS (RFC 1034)
An extra record together with CNAME record except for RRSIG and DS (\fI\%RFC 1034\fP)
.IP \(bu 2
Multiple CNAME record with the same owner
.IP \(bu 2
DNAME record having a record under it (RFC 2672)
DNAME record having a record under it (\fI\%RFC 2672\fP)
.UNINDENT
.sp
Extra checks:
......@@ -1209,7 +1209,7 @@ Possible values:
If your serial was in other than unix time format, be careful
with the transition to unix time. It may happen that the new serial will
be \(aqlower\(aq than the old one. If this is the case, the transition should be
done by hand (see RFC 1982).
done by hand (\fI\%RFC 1982\fP).
.UNINDENT
.UNINDENT
.sp
......
......@@ -149,7 +149,7 @@ identity
--------
An identity of the server returned in the response to the query for TXT
record ``id.server.`` or ``hostname.bind.`` in the CHAOS class (see RFC 4892).
record ``id.server.`` or ``hostname.bind.`` in the CHAOS class (:rfc:`4892`).
Set empty value to disable.
*Default:* FQDN hostname
......@@ -161,7 +161,7 @@ version
A version of the server software returned in the response to the query
for TXT record ``version.server.`` or ``version.bind.`` in the CHAOS
class (see RFC 4892). Set empty value to disable.
class (:rfc:`4892`). Set empty value to disable.
*Default:* server version
......@@ -170,7 +170,7 @@ class (see RFC 4892). Set empty value to disable.
nsid
----
A DNS name server identifier (see RFC 5001). Set empty value to disable.
A DNS name server identifier (:rfc:`5001`). Set empty value to disable.
*Default:* FQDN hostname
......@@ -1198,10 +1198,10 @@ logged only.
Mandatory checks:
- SOA record missing in the zone (RFC 1034)
- An extra record together with CNAME record except for RRSIG and DS (RFC 1034)
- SOA record missing in the zone (:rfc:`1034`)
- An extra record together with CNAME record except for RRSIG and DS (:rfc:`1034`)
- Multiple CNAME record with the same owner
- DNAME record having a record under it (RFC 2672)
- DNAME record having a record under it (:rfc:`2672`)
Extra checks:
......@@ -1369,7 +1369,7 @@ Possible values:
If your serial was in other than unix time format, be careful
with the transition to unix time. It may happen that the new serial will
be \'lower\' than the old one. If this is the case, the transition should be
done by hand (see RFC 1982).
done by hand (:rfc:`1982`).
*Default:* increment
......
......@@ -22,7 +22,7 @@ a DNSSEC validating resolver.
Differences from statically signed zones:
* The NSEC records are constructed as Minimally Covering NSEC Records
(see Appendix A in :rfc:`7129`). Therefore the generated domain names cover
(:rfc:`7129#appendix-A`). Therefore the generated domain names cover
the complete domain name space in the zone's authority.
* NXDOMAIN responses are promoted to NODATA responses. The module proves
......
......@@ -174,7 +174,7 @@ If enabled, outgoing response code is counted:
reply-nodata
............
If enabled, NODATA pseudo RCODE (see RFC 2308, Section 2.2) is counted by the
If enabled, NODATA pseudo RCODE (:rfc:`2308#section-2.2`) is counted by the
query type:
* A
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment