327N/ACopyright (C) 2004 Internet Systems Consortium, Inc. ("ISC")

327N/ACopyright (C) 2001 Internet Software Consortium.

327N/ASee COPYRIGHT in the source root or http://isc.org/copyright.html for terms.

327N/A

327N/ABIND 9 is striving for strict compliance with IETF standards. We

327N/Abelieve this release of BIND 9 complies with the following RFCs, with

327N/Athe caveats and exceptions listed in the numbered notes below. Note

327N/Athat a number of these RFCs do not have the status of Internet

327N/Astandards but are proposed or draft standards, experimental RFCs,

327N/Aor Best Current Practice (BCP) documents. The list is non exhaustive.

327N/A

327N/A RFC1034

327N/A RFC1035 [1] [2]

327N/A RFC1123

327N/A RFC1183

327N/A RFC1535

327N/A RFC1536

327N/A RFC1706

327N/A RFC1712

327N/A RFC1750

327N/A RFC1876

327N/A RFC1982

3817N/A RFC1995

327N/A RFC1996

327N/A RFC2136

327N/A RFC2163

327N/A RFC2181

864N/A RFC2230

864N/A RFC2308

327N/A RFC2536

824N/A RFC2538

327N/A RFC2539

618N/A RFC2671

327N/A RFC2672

844N/A RFC2673

844N/A RFC2782

327N/A RFC2915

1258N/A RFC2930

327N/A RFC2931 [5]

2899N/A RFC3007

2899N/A RFC3110

3817N/A RFC3123

3817N/A RFC3225

3817N/A RFC3226

327N/A RFC3363 [6]

327N/A RFC3490 [7]

327N/A RFC3491 [7]

327N/A RFC3493

327N/A RFC3496

327N/A RFC3597

327N/A RFC3645

327N/A RFC4025

327N/A RFC4034

327N/A RFC4035

327N/A RFC4074

327N/A RFC4255

327N/A RFC4294 - Section 5.1 [8]

327N/A

327N/AThe following DNS related RFC have been obsoleted

327N/A

327N/A RFC2535 (Obsoleted by 4034, 4035) [3] [4]

327N/A RFC2537 (Obsoleted by 3110)

327N/A RFC3008 (Obsoleted by 4034, 4035)

327N/A RFC3152 (Obsoleted by 3596)

824N/A RFC3445 (Obsoleted by 4034, 4035)

327N/A RFC3655 (Obsoleted by 4034, 4035)

327N/A RFC3658 (Obsoleted by 4034, 4035)

327N/A RFC3755 (Obsoleted by 4034, 4035)

327N/A RFC3757 (Obsoleted by 4034, 4035)

327N/A RFC3845 (Obsoleted by 4034, 4035)

327N/A

327N/A[1] Queries to zones that have failed to load return SERVFAIL rather

327N/Athan a non-authoritative response. This is considered a feature.

327N/A

327N/A[2] CLASS ANY queries are not supported. This is considered a feature.

1938N/A

327N/A[3] Wildcard records are not supported in DNSSEC secure zones.

327N/A

3477N/A[4] Servers authoritative for secure zones being resolved by BIND 9

3477N/Amust support EDNS0 (RFC2671), and must return all relevant SIGs and

2023N/ANXTs in responses rather than relying on the resolving server to

327N/Aperform separate queries for missing SIGs and NXTs.

2023N/A

327N/A[5] When receiving a query signed with a SIG(0), the server will only

2023N/Abe able to verify the signature if it has the key in its local

327N/Aauthoritative data; it will not do recursion or validation to

327N/Aretrieve unknown keys.

3817N/A

3817N/A[6] Section 4 is ignored.

3817N/A

3817N/A[7] Requires --with-idn to enable entry of IDN labels within dig,

3817N/Ahost and nslookup at compile time. ACE labels are supported

3817N/Aeverywhere with or without --with-idn.

3817N/A

3817N/A[8] Section 5.1 - DNAME records are fully supported.

3817N/A