The pathname of the file the server dumps -the database to when it receives SIGINT signal -(ndc dumpdb). If not specified, the default is rndc dumpdb. +If not specified, the default is named_dump.db.
Note: Not -yet implemented in Not yet implemented in BIND 9.
named.memstats.+Note: Not -yet implemented in Not yet implemented in BIND 9.
The pathname of the file the server appends statistics -to. If not specified, the default is rndc stats. +If not specified, the default is named.stats.
in the +server's current directory. The format of the file is described +in Section 6.2.14.13BIND 9 currently does not check for multiple CNAMEs -in zone data loaded from master files, but such checks may be introduced -in a later release. BIND 9 always strictly enforces the CNAME rules -in dynamic updates. 9.1 always strictly +enforces the CNAME rules both in master files and dynamic updates. statistics-file option listed above.. See also Section 6.2.14.13. use-ixfr
This option is obsolete. +If you need to disable IXFR to a particular server or servers see +the information on the provide-ixfr option +in Section 6.2.16. See also +Section 4.2. treat-cr-as-space
6.2.14.2. Forwarding
6.2.14.4. Interfaces
6.2.14.5. Query Address
6.2.14.7. Resource Limits
6.2.14.8. Periodic Task Intervals
6.2.14.13. Deprecated Features6.2.14.13. The Statistics File
The statistics file generated by BIND 9 +is similar, but not identical, to that +generated by BIND 8. +
The statistics dump begins with the line +++ Statistics Dump ++++ (973798949), where the number in parentheses is a standard +Unix-style timestamp, measured as seconds since January 1, 1970. Following +that line are a series of lines containing a counter type, the value of the +counter, optionally a zone name, and optionally a view name. +The lines without view and zone listed are global statistics for the entire server. +Lines with a zone and view name for the given view and zone (the view name is +omitted for the default view). The statistics dump ends +with the line --- Statistics Dump --- (973798949), where the +number is identical to the number in the beginning line.
The following statistics counters are maintained:
use-ixfr is deprecated in BIND 9. If - you need to disable IXFR to a particular server or servers see - the information on the success
The number of +successful queries made to the server or zone. A successful query +is defined as query which returns a NOERROR response other than +a referral response.
provide-ixfr option - in Section 6.2.16. See also - Section 4.2.
referralThe number of queries which resulted +in referral responses.
nxrrset
The number of queries which resulted in +NOERROR responses with no data.
nxdomain
The number +of queries which resulted in NXDOMAIN responses.
recursion
The number of queries which caused the server +to perform recursion in order to find the final answer.
failure
The number of queries which resulted in a +failure response other than those above.
6.2.17. trusted-keys
6.2.18. trusted-keys
6.2.19. view
6.2.20. view
6.2.22. zone
6.2.22.1. Zone Types
6.2.22.2. Class
6.2.22.3. Zone Options
Specifies which hosts are allowed to submit Dynamic DNS updates to slave zones to be forwarded to the -master. -This applies only to unsigned updates. -Signed updates are always forwarded. -If there is no acl defined then the server will return NOTIMPL, causing the -client to skip to the next server. If an acl is defined and there is no -match then the default is to deny update forwarding.
{ none; }, which +means that no update forwarding will be performed. To enable +update forwarding, specify allow-update-forwarding { any; };. +Specifying values other than { none; } or +{ any; } is usually counterproductive, since +the responsibility for update access control should rest with the +master server, not the slaves. + +Note that enabling the update forwarding feature on a slave server +may expose master servers relying on insecure IP address based +access control to attacks; see Section 7.3 +for more details.
6.3. Zone File
6.3.1.1. Resource Records
6.3.1.2. Textual expression of RRs
6.3.2. Discussion of MX Records
6.3.4. Inverse Mapping in IPv4
6.3.5. Other Zone File Directives
6.3.5.1. The $ORIGIN
6.3.5.2. The $INCLUDE
6.3.5.3. The $TTL
6.3.6. BIND
7.2. chroot 7.3. Dynamic UpdatesDynamic Update Security 7.2. chroot
7.2.1. The chroot
7.2.2. Using the setuid
7.3. Dynamic Updates7.3. Dynamic Update Security
Access to the dynamic diff --git a/doc/arm/Bv9ARM.ch08.html b/doc/arm/Bv9ARM.ch08.html index 0adf23f32e..9641043ba1 100644 --- a/doc/arm/Bv9ARM.ch08.html +++ b/doc/arm/Bv9ARM.ch08.html @@ -75,17 +75,17 @@ CLASS="TOC" >
8.1. Common Problems 8.2. Incrementing and Changing the Serial Number 8.3. Where Can I Get Help? 8.1. Common Problems
8.1.1. It's not working; how can I figure out what's wrong?
8.2. Incrementing and Changing the Serial Number
8.3. Where Can I Get Help?
A.1. Acknowledgements A.3. General DNSBibliography (and Suggested Reading) A.5. Format of statistics file A.1. Acknowledgements
A.1.1. A Brief History of the DNS
A.2.1.1. HS = hesiod
A.2.1.2. CH = chaos
A.3. General DNS
A.3.1. IPv6 addresses (A6)
.
Bibliography
Standards
[RFC974] C. Partridge,
[RFC1034] P.V. Mockapetris,
[RFC1035] P. V. Mockapetris,
[RFC2181] R., R. Bush Elz,
[RFC2308] M. Andrews,
[RFC1995] M. Ohta,
[RFC1996] P. Vixie,
[RFC2136] P. Vixie, S. Thomson, Y. Rekhter, and J. Bound,
[RFC2845] P. Vixie, O. Gudmundsson, D. Eastlake, 3rd, and B. Wellington,
Proposed Standards Still Under Development
[RFC1886] S. Thomson and C. Huitema,
[RFC2065] D. Eastlake, 3rd and C. Kaufman,
[RFC2137] D. Eastlake, 3rd,
Other Important RFCs About DNS
[RFC1535] E. Gavron,
[RFC1536] A. Kumar, J. Postel, C. Neuman, P. Danzig, and S. Miller,
[RFC1982] R. Elz and R. Bush,
Resource Record Types
[RFC1183] C.F. Everhart, L. A. Mamakos, R. Ullmann, and P. Mockapetris,
[RFC1706] B. Manning and R. Colella,
[RFC2168] R. Daniel and M. Mealling,
[RFC1876] C. Davis, P. Vixie, T., and I. Dickinson,
[RFC2052] A. Gulbrandsen and P. Vixie,
[RFC2163] A. Allocchio,
[RFC2230] R. Atkinson,
DNS
[RFC1101] P. V. Mockapetris,
[RFC1123] Braden,
[RFC1591] J. Postel,
[RFC2317] H. Eidnes, G. de Groot, and P. Vixie,
DNS
[RFC1537] P. Beertema,
[RFC1912] D. Barr,
[RFC1912] D. Barr,
[RFC2010] B. Manning and P. Vixie,
[RFC2219] M. Hamilton and R. Wright,
Other DNS
[RFC1464] R. Rosenbaum,
[RFC1713] A. Romao,
[RFC1794] T. Brisco,
[RFC2240] O. Vaughan,
[RFC2345] J. Klensin, T. Wolf, and G. Oglesby,
[RFC2352] O. Vaughan,
Obsolete and Unimplemented Experimental RRs
[RFC1712] C. Farrell, M. Schulze, S. Pleitner, and D. Baldoni,
A.4.3. Other Documents About BIND
Bibliography
A.5. Format of statistics file
The statistics file generated by BIND 9 -is similar in form to that -generated by BIND 8, but is not identical, -due to differences in the counters -currently implemented in BIND 9. -
The statistics dump begins with the line +++ Statistics Dump -+++ (973798949), where the number in parentheses is a standard -Unix-style timestamp, measured as seconds since January 1, 1970. Following -that line are a series of lines containing a counter type, value of the -counter, and possibly a view/zone pair. The lines without view and zone -listed are global counters for the entire server and the lines with view and -zones specified are for the given view and zone. The statistics dump ends -with the line --- Statistics Dump --- (973798949), where the -number is identical to the number in the beginning line.
The following counters are defined:
success
This counter is used to track the number of -successful queries made to the server or zone. A successful query -is defined as query which returns a NOERROR result other than -delegation replies.
delegation
This counter is used to track the number -of queries which return delegations instead a final answer.
nxrrset
This counter is used to track the number -of queries made which return a result code of NXRRSET.
nxdomain
This counter is used to track the number -of queries made which return a result code of NXDOMAIN.
recursion
This counter is used to track the number -of queries made which resulted in recursion in order to find the final -answer.
failure
This counter is used to track the number -of queries resulted in a SERVFAIL reply.
6.2.17. trusted-keys 6.2.18. trusted-keys 6.2.19. view 6.2.20. view 6.2.22. zone 6.3. Zone File 6.3.2. Discussion of MX Records 6.3.4. Inverse Mapping in IPv4 6.3.5. Other Zone File Directives 6.3.6. BIND 7.2. chroot
- A.1. Acknowledgements
- A.1.1. A Brief History of the DNS
- A.3. General DNS
- A.3.1. IPv6 addresses (A6)
- A.4.3. Other Documents About BIND
A.5. Format of statistics file