Network Working Group M. Andrews
Internet-Draft ISC
-Intended status: BCP June 5, 2008
-Expires: December 7, 2008
+Intended status: BCP November 19, 2009
+Expires: May 23, 2010
Locally-served DNS Zones
- draft-ietf-dnsop-default-local-zones-05
+ draft-ietf-dnsop-default-local-zones-09
+
+Abstract
+
+ Experience with the Domain Name System (DNS) has shown that there are
+ a number of DNS zones all iterative resolvers and recursive
+ nameservers should automatically serve, unless configured otherwise.
+ RFC 4193 specifies that this should occur for D.F.IP6.ARPA. This
+ document extends the practice to cover the IN-ADDR.ARPA zones for RFC
+ 1918 address space and other well known zones with similar
+ characteristics.
Status of this Memo
- By submitting this Internet-Draft, each author represents that any
- applicable patent or other IPR claims of which he or she is aware
- have been or will be disclosed, and any of which he or she becomes
- aware will be disclosed, in accordance with Section 6 of BCP 79.
+ This Internet-Draft is submitted to IETF in full conformance with the
+ provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
- This Internet-Draft will expire on December 7, 2008.
+ This Internet-Draft will expire on May 23, 2010.
+
+Copyright Notice
+
+ Copyright (c) 2009 IETF Trust and the persons identified as the
+ document authors. All rights reserved.
+
+ This document is subject to BCP 78 and the IETF Trust's Legal
+
+
+
+Andrews Expires May 23, 2010 [Page 1]
+\f
+Internet-Draft Locally-served DNS Zones November 2009
+
+
+ Provisions Relating to IETF Documents
+ (http://trustee.ietf.org/license-info) in effect on the date of
+ publication of this document. Please review these documents
+ carefully, as they describe your rights and restrictions with respect
+ to this document. Code Components extracted from this document must
+ include Simplified BSD License text as described in Section 4.e of
+ the Trust Legal Provisions and are provided without warranty as
+ described in the BSD License.
+
+ This document may contain material from IETF Documents or IETF
+ Contributions published or made publicly available before November
+ 10, 2008. The person(s) controlling the copyright in some of this
+ material may not have granted the IETF Trust the right to allow
+ modifications of such material outside the IETF Standards Process.
+ Without obtaining an adequate license from the person(s) controlling
+ the copyright in such materials, this document may not be modified
+ outside the IETF Standards Process, and derivative works of it may
+ not be created outside the IETF Standards Process, except to format
+ it for publication as an RFC or to translate it into languages other
+ than English.
+
+
+
+
+
+
+
+
+
+
+
+
+
-Abstract
- Experience has shown that there are a number of DNS zones all
- iterative resolvers and recursive nameservers should, unless
- configured otherwise, automatically serve. RFC 4193 specifies that
- this should occur for D.F.IP6.ARPA. This document extends the
- practice to cover the IN-ADDR.ARPA zones for RFC 1918 address space
- and other well known zones with similar characteristics.
-Andrews Expires December 7, 2008 [Page 1]
+
+
+
+
+
+
+
+Andrews Expires May 23, 2010 [Page 2]
\f
-Internet-Draft Locally-served DNS Zones June 2008
+Internet-Draft Locally-served DNS Zones November 2009
Table of Contents
2. Effects on sites using RFC 1918 addresses. . . . . . . . . . . 4
3. Changes to Iterative Resolver Behaviour. . . . . . . . . . . . 4
4. Lists Of Zones Covered . . . . . . . . . . . . . . . . . . . . 5
- 4.1. RFC 1918 Zones . . . . . . . . . . . . . . . . . . . . . . 5
- 4.2. RFC 3330 Zones . . . . . . . . . . . . . . . . . . . . . . 6
+ 4.1. RFC1918 Zones . . . . . . . . . . . . . . . . . . . . . . 5
+ 4.2. RFC3330 Zones . . . . . . . . . . . . . . . . . . . . . . 6
4.3. Local IPv6 Unicast Addresses . . . . . . . . . . . . . . . 6
4.4. IPv6 Locally Assigned Local Addresses . . . . . . . . . . 6
4.5. IPv6 Link Local Addresses . . . . . . . . . . . . . . . . 7
+ 4.6. IPv6 Example Prefix . . . . . . . . . . . . . . . . . . . 7
5. Zones that are Out-Of-Scope . . . . . . . . . . . . . . . . . 7
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
7. Security Considerations . . . . . . . . . . . . . . . . . . . 8
- 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 8
- 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8
- 9.1. Normative References . . . . . . . . . . . . . . . . . . . 8
+ 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 9
+ 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9
+ 9.1. Normative References . . . . . . . . . . . . . . . . . . . 9
9.2. Informative References . . . . . . . . . . . . . . . . . . 10
Appendix A. Change History [To Be Removed on Publication] . . . . 10
- A.1. draft-ietf-dnsop-default-local-zones-05.txt . . . . . . . 10
- A.2. draft-ietf-dnsop-default-local-zones-04.txt . . . . . . . 10
- A.3. draft-ietf-dnsop-default-local-zones-03.txt . . . . . . . 10
- A.4. draft-ietf-dnsop-default-local-zones-02.txt . . . . . . . 10
- A.5. draft-ietf-dnsop-default-local-zones-01.txt . . . . . . . 11
- A.6. draft-ietf-dnsop-default-local-zones-00.txt . . . . . . . 11
- A.7. draft-andrews-full-service-resolvers-03.txt . . . . . . . 11
- A.8. draft-andrews-full-service-resolvers-02.txt . . . . . . . 11
- Appendix B. Proposed Status [To Be Removed on Publication] . . . 11
- Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 11
- Intellectual Property and Copyright Statements . . . . . . . . . . 12
+ A.1. draft-ietf-dnsop-default-local-zones-09.txt . . . . . . . 10
+ A.2. draft-ietf-dnsop-default-local-zones-08.txt . . . . . . . 10
+ A.3. draft-ietf-dnsop-default-local-zones-07.txt . . . . . . . 10
+ A.4. draft-ietf-dnsop-default-local-zones-06.txt . . . . . . . 10
+ A.5. draft-ietf-dnsop-default-local-zones-05.txt . . . . . . . 11
+ A.6. draft-ietf-dnsop-default-local-zones-04.txt . . . . . . . 11
+ A.7. draft-ietf-dnsop-default-local-zones-03.txt . . . . . . . 11
+ A.8. draft-ietf-dnsop-default-local-zones-02.txt . . . . . . . 11
+ A.9. draft-ietf-dnsop-default-local-zones-01.txt . . . . . . . 11
+ A.10. draft-ietf-dnsop-default-local-zones-00.txt . . . . . . . 11
+ A.11. draft-andrews-full-service-resolvers-03.txt . . . . . . . 11
+ A.12. draft-andrews-full-service-resolvers-02.txt . . . . . . . 12
+ Appendix B. Proposed Status [To Be Removed on Publication] . . . 12
+ Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 12
-
-
-
-
-Andrews Expires December 7, 2008 [Page 2]
+Andrews Expires May 23, 2010 [Page 3]
\f
-Internet-Draft Locally-served DNS Zones June 2008
+Internet-Draft Locally-served DNS Zones November 2009
1. Introduction
- Experience has shown that there are a number of DNS [RFC 1034] [RFC
- 1035] zones that all iterative resolvers and recursive nameservers
- SHOULD, unless intentionally configured otherwise, automatically
- serve. These zones include, but are not limited to, the IN-ADDR.ARPA
- zones for the address space allocated by [RFC 1918] and the IP6.ARPA
- zones for locally assigned unique local IPv6 addresses, [RFC 4193].
+ Experience with the Domain Name System (DNS, [RFC1034] and [RFC1035])
+ has shown that there are a number of DNS zones that all iterative
+ resolvers and recursive nameservers SHOULD automatically serve,
+ unless intentionally configured otherwise. These zones include, but
+ are not limited to, the IN-ADDR.ARPA zones for the address space
+ allocated by [RFC1918] and the IP6.ARPA zones for locally assigned
+ unique local IPv6 addresses defined in [RFC4193].
This recommendation is made because data has shown that significant
leakage of queries for these name spaces is occurring, despite
configuration will address all these issues for the zones listed in
Section 4.
- [RFC 4193] recommends that queries for D.F.IP6.ARPA be handled
+ [RFC4193] recommends that queries for D.F.IP6.ARPA be handled
locally. This document extends the recommendation to cover the IN-
- ADDR.ARPA zones for [RFC 1918] and other well known IN-ADDR.ARPA and
+ ADDR.ARPA zones for [RFC1918] and other well known IN-ADDR.ARPA and
IP6.ARPA zones for which queries should not appear on the public
Internet.
[AS112] will not have to be increased, and may in time be reduced.
This recommendation should also help DNS responsiveness for sites
- which are using [RFC 1918] addresses but do not follow the last
- paragraph in Section 3 of [RFC 1918].
+ which are using [RFC1918] addresses but do not follow the last
+ paragraph in Section 3 of [RFC1918].
1.1. Reserved Words
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
- document are to be interpreted as described in [RFC 2119].
-
+ document are to be interpreted as described in [RFC2119].
-Andrews Expires December 7, 2008 [Page 3]
+Andrews Expires May 23, 2010 [Page 4]
\f
-Internet-Draft Locally-served DNS Zones June 2008
+Internet-Draft Locally-served DNS Zones November 2009
2. Effects on sites using RFC 1918 addresses.
- For most sites using [RFC 1918] addresses, the changes here will have
+ For most sites using [RFC1918] addresses, the changes here will have
little or no detrimental effect. If the site does not already have
the reverse tree populated the only effect will be that the name
error responses will be generated locally rather than remotely.
recommendation will not be relevant.
The most significant impact will be felt at sites that make use of
- delegations for [RFC 1918] addresses and have populated these zones.
+ delegations for [RFC1918] addresses and have populated these zones.
These sites will need to override the default configuration expressed
in this document to allow resolution to continue. Typically, such
sites will be fully disconnected from the Internet and have their own
zones in Section 4, with the obvious exception of queries for the
zone name itself where SOA, NS and "no data" responses will be
returned as appropriate to the query type. One common way to do this
- is to serve empty (SOA and NS only) zones.
+ all at once is to serve empty (SOA and NS only) zones.
An implementation of this recommendation MUST provide a mechanism to
disable this new behaviour, and SHOULD allow this decision on a zone
Internet servers. This document recommends that the NS record
defaults to the name of the zone and the SOA MNAME defaults to the
name of the only NS RR's target. The SOA RNAME should default to
- "nobody.invalid." [RFC 2606]. Implementations SHOULD provide a
+ "nobody.invalid." [RFC2606]. Implementations SHOULD provide a
mechanism to set these values. No address records need to be
provided for the name server.
-Andrews Expires December 7, 2008 [Page 4]
+Andrews Expires May 23, 2010 [Page 5]
\f
-Internet-Draft Locally-served DNS Zones June 2008
+Internet-Draft Locally-served DNS Zones November 2009
- The SOA RR is needed to support negative caching [RFC 2308] of name
+ The SOA RR is needed to support negative caching [RFC2308] of name
error responses and to point clients to the primary master for DNS
dynamic updates.
SOA timer values MAY be chosen arbitrarily since they are not
intended to control any zone transfer activity.
- The NS RR is needed as some UPDATE [RFC 2136] clients use NS queries
+ The NS RR is needed as some UPDATE [RFC2136] clients use NS queries
to discover the zone to be updated. Having no address records for
the name server is expected to abort UPDATE processing in the client.
requested in the IANA Considerations Section. The zone name is the
entity to be registered.
-4.1. RFC 1918 Zones
+4.1. RFC1918 Zones
The following zones correspond to the IPv4 address space reserved in
- [RFC 1918].
+ [RFC1918].
+----------------------+
| Zone |
-Andrews Expires December 7, 2008 [Page 5]
+Andrews Expires May 23, 2010 [Page 6]
\f
-Internet-Draft Locally-served DNS Zones June 2008
+Internet-Draft Locally-served DNS Zones November 2009
-4.2. RFC 3330 Zones
+4.2. RFC3330 Zones
- The following zones correspond to those address ranges from [RFC
- 3330] that are not expected to appear as source or destination
- addresses on the public Internet and to not have a unique name to
- associate with.
+ The following zones correspond to those address ranges from [RFC3330]
+ that are not expected to appear as source or destination addresses on
+ the public Internet and to not have a unique name to associate with.
The recommendation to serve an empty zone 127.IN-ADDR.ARPA is not a
attempt to discourage any practice to provide a PTR RR for
4.3. Local IPv6 Unicast Addresses
- The reverse mappings ([RFC 3596], Section 2.5 IP6.ARPA Domain) for
- the IPv6 Unspecified (::) and Loopback (::1) addresses ([RFC 4291],
+ The reverse mappings ([RFC3596], Section 2.5 IP6.ARPA Domain) for the
+ IPv6 Unspecified (::) and Loopback (::1) addresses ([RFC4291],
Sections 2.4, 2.5.2 and 2.5.3) are covered by these two zones:
+-------------------------------------------+
| Zone |
+-------------------------------------------+
| 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.\ |
- | 0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA |
+ | 0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA |
| 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.\ |
- | 0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA |
+ | 0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA |
+-------------------------------------------+
Note: Line breaks and a escapes '\' have been inserted above for
4.4. IPv6 Locally Assigned Local Addresses
- Section 4.4 of [RFC 4193] already required special treatment of:
+ Section 4.4 of [RFC4193] already required special treatment of:
+
-Andrews Expires December 7, 2008 [Page 6]
+Andrews Expires May 23, 2010 [Page 7]
\f
-Internet-Draft Locally-served DNS Zones June 2008
+Internet-Draft Locally-served DNS Zones November 2009
+--------------+
4.5. IPv6 Link Local Addresses
- IPv6 Link-Local Addresses as of [RFC 4291], Section 2.5.6 are covered
+ IPv6 Link-Local Addresses as of [RFC4291], Section 2.5.6 are covered
by four distinct reverse DNS zones:
+----------------+
| B.E.F.IP6.ARPA |
+----------------+
+4.6. IPv6 Example Prefix
+
+ IPv6 example prefix [RFC3849].
+
+ +--------------------------+
+ | Zone |
+ +--------------------------+
+ | 8.B.D.0.1.0.0.2.IP6.ARPA |
+ +--------------------------+
+
+ Note: 8.B.D.0.1.0.0.2.IP6.ARPA is not being used as a example here.
+
5. Zones that are Out-Of-Scope
- IPv6 site-local addresses, [RFC 4291] Sections 2.4 and 2.5.7, and
- IPv6 Non-Locally Assigned Local addresses [RFC 4193] are not covered
- here. It is expected that IPv6 site-local addresses will be self
- correcting as IPv6 implementations remove support for site-local
- addresses. However, sacrificial servers for C.E.F.IP6.ARPA through
+ IPv6 site-local addresses (deprecated, see [RFC4291] Sections 2.4 and
+ 2.5.7), and IPv6 Non-Locally Assigned Local addresses ([RFC4193]) are
+ not covered here.
+
+ It is expected that IPv6 site-local addresses will be self correcting
+ as IPv6 implementations remove support for site-local addresses.
+ However, sacrificial servers for the zones C.E.F.IP6.ARPA through
F.E.F.IP6.ARPA may still need to be deployed in the short term if the
traffic becomes excessive.
- For IPv6 Non-Locally Assigned Local addresses (L = 0) [RFC 4193],
+ For IPv6 Non-Locally Assigned Local addresses (L = 0) [RFC4193],
there has been no decision made about whether the Regional Internet
Registries (RIRs) will provide delegations in this space or not. If
+
+
+
+Andrews Expires May 23, 2010 [Page 8]
+\f
+Internet-Draft Locally-served DNS Zones November 2009
+
+
they don't, then C.F.IP6.ARPA will need to be added to the list in
Section 4.4. If they do, then registries will need to take steps to
ensure that name servers are provided for these addresses.
This document also ignores IP6.INT. IP6.INT has been wound up with
only legacy resolvers now generating reverse queries under IP6.INT
- [RFC 4159].
+ [RFC4159].
This document has also deliberately ignored names immediately under
the root domain. While there is a subset of queries to the root name
for unqualified hostnames, IPv6 addresses).
-
-Andrews Expires December 7, 2008 [Page 7]
-\f
-Internet-Draft Locally-served DNS Zones June 2008
-
-
6. IANA Considerations
This document requests that IANA establish a registry of zones which
- require this default behaviour. The initial contents of which are in
- Section 4. Implementors are encouraged to check this registry and
- adjust their implementations to reflect changes therein.
+ require this default behaviour. The initial contents of this
+ registry are defined in Section 4. Implementors are encouraged to
+ periodically check this registry and adjust their implementations to
+ reflect changes therein.
- This registry can be amended through "IETF Consensus" as per [RFC
- 2434].
+ This registry can be amended through "IETF Review" as per [RFC5226].
IANA should co-ordinate with the RIRs to ensure that, as DNSSEC is
deployed in the reverse tree, delegations for these zones are made in
7. Security Considerations
- During the initial deployment phase, particularly where [RFC 1918]
+ During the initial deployment phase, particularly where [RFC1918]
addresses are in use, there may be some clients that unexpectedly
receive a name error rather than a PTR record. This may cause some
service disruption until their recursive name server(s) have been re-
being answered from the delegated servers.
It is recommended that sites actively using these namespaces secure
- them using DNSSEC [RFC 4035] by publishing and using DNSSEC trust
+ them using DNSSEC [RFC4035] by publishing and using DNSSEC trust
anchors. This will protect the clients from accidental import of
+
+
+
+Andrews Expires May 23, 2010 [Page 9]
+\f
+Internet-Draft Locally-served DNS Zones November 2009
+
+
unsigned responses from the Internet.
9.1. Normative References
- [RFC 1034]
- Mockapetris, P., "DOMAIN NAMES - CONCEPTS AND FACILITIES",
+ [RFC1034] Mockapetris, P., "DOMAIN NAMES - CONCEPTS AND FACILITIES",
STD 13, RFC 1034, November 1987.
-
-
-Andrews Expires December 7, 2008 [Page 8]
-\f
-Internet-Draft Locally-served DNS Zones June 2008
-
-
- [RFC 1035]
- Mockapetris, P., "DOMAIN NAMES - IMPLEMENTATION AND
+ [RFC1035] Mockapetris, P., "DOMAIN NAMES - IMPLEMENTATION AND
SPECIFICATION", STD 13, RFC 1035, November 1987.
- [RFC 1918]
- Rekhter, Y., Moskowitz, B., Karrenberg, D., de Groot, G.,
+ [RFC1918] Rekhter, Y., Moskowitz, B., Karrenberg, D., de Groot, G.,
and E. Lear, "Address Allocation for Private Internets",
BCP 5, RFC 1918, February 1996.
- [RFC 2119]
- Bradner, S., "Key words for use in RFCs to Indicate
+ [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
- [RFC 2136]
- Vixie, P., Thomson, A., Rekhter, Y., and J. Bound,
+ [RFC2136] Vixie, P., Thomson, A., Rekhter, Y., and J. Bound,
"Dynamic Updates in the Domain Name System (DNS UPDATE)",
RFC 2136, April 1997.
- [RFC 2308]
- Andrews, M., "Negative Caching of DNS Queries (DNS
+ [RFC2308] Andrews, M., "Negative Caching of DNS Queries (DNS
NCACHE)", RFC 2398, March 1998.
- [RFC 2434]
- Narten, T. and H. Alvestrand, "Guidelines for Writing an
- IANA Considerations Section in RFCs", BCP 26, RFC 2434,
- October 1998.
-
- [RFC 2606]
- Eastlake, D. and A. Panitz, "Reserved Top Level DNS
+ [RFC2606] Eastlake, D. and A. Panitz, "Reserved Top Level DNS
Names", BCP 32, RFC 2606, June 1999.
- [RFC 3596]
- Thomson, S., Huitema, C., Ksinant, V., and M. Souissi,
+ [RFC3596] Thomson, S., Huitema, C., Ksinant, V., and M. Souissi,
"DNS Extensions to Support IPv6", RFC 3596, October 2003.
- [RFC 4035]
- Arends, R., Austein, R., Larson, M., Massey, D., and S.
+ [RFC4035] Arends, R., Austein, R., Larson, M., Massey, D., and S.
Rose, "Protocol Modifications for the DNS Security
Extensions", RFC 4035, March 2005.
- [RFC 4159]
- Huston, G., "Deprecation of "ip6.int"", BCP 109, RFC 4159,
+ [RFC4159] Huston, G., "Deprecation of "ip6.int"", BCP 109, RFC 4159,
August 2005.
- [RFC 4193]
- Hinden, R. and B. Haberman, "Unique Local IPv6 Unicast
+ [RFC4193] Hinden, R. and B. Haberman, "Unique Local IPv6 Unicast
Addresses", RFC 4193, October 2005.
-
-Andrews Expires December 7, 2008 [Page 9]
+Andrews Expires May 23, 2010 [Page 10]
\f
-Internet-Draft Locally-served DNS Zones June 2008
+Internet-Draft Locally-served DNS Zones November 2009
- [RFC 4291]
- Hinden, R. and S. Deering, "IP Version 6 Addressing
+ [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, February 2006.
+ [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
+ IANA Considerations Section in RFCs", BCP 26, RFC 5226,
+ October 2008.
+
9.2. Informative References
[AS112] "AS112 Project", <http://www.as112.net/>.
[I-D.draft-ietf-dnsop-as112-ops]
Abley, J. and W. Maton, "AS112 Nameserver Operations",
- draft-ietf-dnsop-as112-ops-00 (work in progress),
- February 2007.
+ draft-ietf-dnsop-as112-ops-01 (work in progress),
+ November 2007.
[I-D.draft-ietf-dnsop-as112-under-attack-help-help]
Abley, J. and W. Maton, "I'm Being Attacked by
PRISONER.IANA.ORG!",
- draft-ietf-dnsop-as112-under-attack-help-help-00 (work in
- progress), February 2007.
+ draft-ietf-dnsop-as112-under-attack-help-help-01 (work in
+ progress), November 2007.
+
+ [RFC3330] "Special-Use IPv4 Addresses", RFC 3330, September 2002.
- [RFC 3330]
- "Special-Use IPv4 Addresses", RFC 3330, September 2002.
+ [RFC3849] Huston, G., Lord, A., and P. Smith, "IPv6 Address Prefix
+ Reserved for Documentation", RFC 3849, July 2004.
Appendix A. Change History [To Be Removed on Publication]
-A.1. draft-ietf-dnsop-default-local-zones-05.txt
+A.1. draft-ietf-dnsop-default-local-zones-09.txt
+
+ refresh awaiting writeup
+
+A.2. draft-ietf-dnsop-default-local-zones-08.txt
+
+ editorial, reference updates
+
+A.3. draft-ietf-dnsop-default-local-zones-07.txt
+
+ none, expiry prevention
+
+A.4. draft-ietf-dnsop-default-local-zones-06.txt
+
+ add IPv6 example prefix
+
+
+
+
+
+
+Andrews Expires May 23, 2010 [Page 11]
+\f
+Internet-Draft Locally-served DNS Zones November 2009
+
+
+A.5. draft-ietf-dnsop-default-local-zones-05.txt
none, expiry prevention
-A.2. draft-ietf-dnsop-default-local-zones-04.txt
+A.6. draft-ietf-dnsop-default-local-zones-04.txt
Centrally Assigned Local addresses -> Non-Locally Assigned Local
address
-A.3. draft-ietf-dnsop-default-local-zones-03.txt
+A.7. draft-ietf-dnsop-default-local-zones-03.txt
expanded section 4 descriptions
- Added references [RFC 2136], [RFC 3596],
+ Added references [RFC2136], [RFC3596],
[I-D.draft-ietf-dnsop-as112-ops] and
[I-D.draft-ietf-dnsop-as112-under-attack-help-help].
Revised language.
-A.4. draft-ietf-dnsop-default-local-zones-02.txt
+A.8. draft-ietf-dnsop-default-local-zones-02.txt
RNAME now "nobody.invalid."
-
-
-
-Andrews Expires December 7, 2008 [Page 10]
-\f
-Internet-Draft Locally-served DNS Zones June 2008
-
-
Revised language.
-A.5. draft-ietf-dnsop-default-local-zones-01.txt
+A.9. draft-ietf-dnsop-default-local-zones-01.txt
Revised impact description.
Updated to reflect change in IP6.INT status.
-A.6. draft-ietf-dnsop-default-local-zones-00.txt
+A.10. draft-ietf-dnsop-default-local-zones-00.txt
Adopted by DNSOP.
Title changed.
-A.7. draft-andrews-full-service-resolvers-03.txt
+A.11. draft-andrews-full-service-resolvers-03.txt
Added "Proposed Status".
-A.8. draft-andrews-full-service-resolvers-02.txt
+
+
+
+
+
+
+Andrews Expires May 23, 2010 [Page 12]
+\f
+Internet-Draft Locally-served DNS Zones November 2009
+
+
+A.12. draft-andrews-full-service-resolvers-02.txt
Added 0.IN-ADDR.ARPA.
-Andrews Expires December 7, 2008 [Page 11]
-\f
-Internet-Draft Locally-served DNS Zones June 2008
-Full Copyright Statement
- Copyright (C) The IETF Trust (2008).
- This document is subject to the rights, licenses and restrictions
- contained in BCP 78, and except as set forth therein, the authors
- retain all their rights.
- This document and the information contained herein are provided on an
- "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
- OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
- THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
- OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
- THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
- WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
-Intellectual Property
- The IETF takes no position regarding the validity or scope of any
- Intellectual Property Rights or other rights that might be claimed to
- pertain to the implementation or use of the technology described in
- this document or the extent to which any license under such rights
- might or might not be available; nor does it represent that it has
- made any independent effort to identify any such rights. Information
- on the procedures with respect to rights in RFC documents can be
- found in BCP 78 and BCP 79.
- Copies of IPR disclosures made to the IETF Secretariat and any
- assurances of licenses to be made available, or the result of an
- attempt made to obtain a general license or permission for the use of
- such proprietary rights by implementers or users of this
- specification can be obtained from the IETF on-line IPR repository at
- http://www.ietf.org/ipr.
- The IETF invites any interested party to bring to its attention any
- copyrights, patents or patent applications, or other proprietary
- rights that may cover technology that may be required to implement
- this standard. Please address the information to the IETF at
- ietf-ipr@ietf.org.
-Andrews Expires December 7, 2008 [Page 12]
+
+Andrews Expires May 23, 2010 [Page 13]
\f
+
projects / thirdparty / bind9.git / commitdiff
