rfc-compliance revision 6211baaa66d7cac28a21b6426681e597ff04ca9e
420bfee669b4ac21320f24c5d92e9857866b710ebnicholesCopyright (C) 2000, 2001 Internet Software Consortium.
420bfee669b4ac21320f24c5d92e9857866b710ebnicholesSee COPYRIGHT in the source root or http://isc.org/copyright.html for terms.
420bfee669b4ac21320f24c5d92e9857866b710ebnicholes
420bfee669b4ac21320f24c5d92e9857866b710ebnicholes$Id: rfc-compliance,v 1.1 2001/02/22 19:53:08 gson Exp $
420bfee669b4ac21320f24c5d92e9857866b710ebnicholes
ac7985784d08a3655291f24f711812b4d8b1cbcffuankgBIND 9 is striving for strict compliance with IETF standards. We
420bfee669b4ac21320f24c5d92e9857866b710ebnicholesbelieve this release of BIND 9 complies with the following RFCs, with
420bfee669b4ac21320f24c5d92e9857866b710ebnicholesthe caveats and exceptions listed in the numbered notes below. Note
420bfee669b4ac21320f24c5d92e9857866b710ebnicholesthat a number of these RFCs do not have the status of Internet
420bfee669b4ac21320f24c5d92e9857866b710ebnicholesstandards but are proposed or draft standards, experimental RFCs,
420bfee669b4ac21320f24c5d92e9857866b710ebnicholesor Best Current Practice (BCP) documents.
420bfee669b4ac21320f24c5d92e9857866b710ebnicholes
0662ed52e814f8f08ef0e09956413a792584eddffuankg RFC1034
420bfee669b4ac21320f24c5d92e9857866b710ebnicholes RFC1035 [1] [2]
420bfee669b4ac21320f24c5d92e9857866b710ebnicholes RFC1123
420bfee669b4ac21320f24c5d92e9857866b710ebnicholes RFC1183
420bfee669b4ac21320f24c5d92e9857866b710ebnicholes RFC1535
420bfee669b4ac21320f24c5d92e9857866b710ebnicholes RFC1536
420bfee669b4ac21320f24c5d92e9857866b710ebnicholes RFC1706
420bfee669b4ac21320f24c5d92e9857866b710ebnicholes RFC1712
420bfee669b4ac21320f24c5d92e9857866b710ebnicholes RFC1750
420bfee669b4ac21320f24c5d92e9857866b710ebnicholes RFC1876
420bfee669b4ac21320f24c5d92e9857866b710ebnicholes RFC1982
420bfee669b4ac21320f24c5d92e9857866b710ebnicholes RFC1995
420bfee669b4ac21320f24c5d92e9857866b710ebnicholes RFC1996
420bfee669b4ac21320f24c5d92e9857866b710ebnicholes RFC2136
70953fb44a7140fe206c3a5f011e24209c8c5c6abnicholes RFC2163
70953fb44a7140fe206c3a5f011e24209c8c5c6abnicholes RFC2181
44f575c8cb19a7a5cd61664a7848be6bc197df02fuankg RFC2230
44f575c8cb19a7a5cd61664a7848be6bc197df02fuankg RFC2308
44f575c8cb19a7a5cd61664a7848be6bc197df02fuankg RFC2535 [3] [4] [5]
420bfee669b4ac21320f24c5d92e9857866b710ebnicholes RFC2536
420bfee669b4ac21320f24c5d92e9857866b710ebnicholes RFC2537
420bfee669b4ac21320f24c5d92e9857866b710ebnicholes RFC2538
420bfee669b4ac21320f24c5d92e9857866b710ebnicholes RFC2539
420bfee669b4ac21320f24c5d92e9857866b710ebnicholes RFC2671
420bfee669b4ac21320f24c5d92e9857866b710ebnicholes RFC2672
420bfee669b4ac21320f24c5d92e9857866b710ebnicholes RFC2673
420bfee669b4ac21320f24c5d92e9857866b710ebnicholes RFC2782
420bfee669b4ac21320f24c5d92e9857866b710ebnicholes
420bfee669b4ac21320f24c5d92e9857866b710ebnicholes[1] Queries to zones that have failed to load return SERVFAIL rather
420bfee669b4ac21320f24c5d92e9857866b710ebnicholesthan a non-authoritative response. This is considered a feature.
420bfee669b4ac21320f24c5d92e9857866b710ebnicholes
420bfee669b4ac21320f24c5d92e9857866b710ebnicholes[2] CLASS ANY queries are not supported. This is considered a feature.
420bfee669b4ac21320f24c5d92e9857866b710ebnicholes
420bfee669b4ac21320f24c5d92e9857866b710ebnicholes[3] Wildcard records are not supported in DNSSEC secure zones.
420bfee669b4ac21320f24c5d92e9857866b710ebnicholes
420bfee669b4ac21320f24c5d92e9857866b710ebnicholes[4] Servers authoritative for secure zones being resolved by BIND 9
420bfee669b4ac21320f24c5d92e9857866b710ebnicholesmust support EDNS0 (RFC2671), and must return all relevant SIGs and
420bfee669b4ac21320f24c5d92e9857866b710ebnicholesNXTs in responses rather than relying on the resolving server to
420bfee669b4ac21320f24c5d92e9857866b710ebnicholesperform separate queries for missing SIGs and NXTs.
420bfee669b4ac21320f24c5d92e9857866b710ebnicholes
420bfee669b4ac21320f24c5d92e9857866b710ebnicholes