| CARVIEW |
Select Language
HTTP/2 200
date: Thu, 09 Oct 2025 20:00:13 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
set-cookie: __cf_bm=JX339snd5_hzqSjvJsGVrk3iKeboE6S41iACwZR7vT4-1760040013-1.0.1.1-SUfsS4Dr_EG90hFB.tfmIdvWZyKIAH7KmtDN8b8Rcb3Ul3qU81BTJOylPPkWmqCYGzC1OP4WkHB23bwJnyYphQENuDiY8bvb2unw9Ujkh_g; path=/; expires=Thu, 09-Oct-25 20:30:13 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98c0767d5888c1cc-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 1995 » RFC Editor
Search RFCs
RFC 1995
Incremental Zone Transfer in DNS, August 1996
- File formats:
- Status:
- PROPOSED STANDARD
- Updates:
- RFC 1035
- Updated by:
- RFC 9103
- Author:
- M. Ohta
- Stream:
- IETF
- Source:
- dnsind (int)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC1995
Discuss this RFC: Send questions or comments to the mailing list iesg@ietf.org
Other actions: View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 1995
Abstract
This document proposes extensions to the DNS protocols to provide an incremental zone transfer (IXFR) mechanism. [STANDARDS-TRACK]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us