draft-ietf-dnsop-as112-under-attack-help-help-05.txt   draft-ietf-dnsop-as112-under-attack-help-help-06.txt 
Network Working Group J. Abley Network Working Group J. Abley
Internet-Draft ICANN Internet-Draft ICANN
Intended status: Informational W. Maton Intended status: Informational W. Maton
Expires: September 11, 2011 NRC-CNRC Expires: October 31, 2011 NRC-CNRC
March 10, 2011 April 29, 2011
I'm Being Attacked by PRISONER.IANA.ORG! I'm Being Attacked by PRISONER.IANA.ORG!
draft-ietf-dnsop-as112-under-attack-help-help-05 draft-ietf-dnsop-as112-under-attack-help-help-06
Abstract Abstract
Many sites connected to the Internet make use of IPv4 addresses which Many sites connected to the Internet make use of IPv4 addresses which
are not globally unique. Examples are the addresses designated in are not globally unique. Examples are the addresses designated in
RFC1918 for private use within individual sites. RFC1918 for private use within individual sites.
Hosts should never normally send DNS reverse mapping queries for Hosts should never normally send DNS reverse mapping queries for
those addresses on the public Internet. However, such queries are those addresses on the public Internet. However, such queries are
frequently observed. Authoritative servers are deployed to provide frequently observed. Authoritative servers are deployed to provide
skipping to change at page 1, line 48 skipping to change at page 1, line 48
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 11, 2011. This Internet-Draft will expire on October 31, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 32 skipping to change at page 2, line 32
1. Introduction and Target Audience . . . . . . . . . . . . . . . 3 1. Introduction and Target Audience . . . . . . . . . . . . . . . 3
2. Private-Use Addresses . . . . . . . . . . . . . . . . . . . . 4 2. Private-Use Addresses . . . . . . . . . . . . . . . . . . . . 4
3. DNS Reverse Mapping . . . . . . . . . . . . . . . . . . . . . 5 3. DNS Reverse Mapping . . . . . . . . . . . . . . . . . . . . . 5
4. DNS Reverse Mapping for Private-Use Addresses . . . . . . . . 6 4. DNS Reverse Mapping for Private-Use Addresses . . . . . . . . 6
5. AS112 Nameservers . . . . . . . . . . . . . . . . . . . . . . 7 5. AS112 Nameservers . . . . . . . . . . . . . . . . . . . . . . 7
6. Inbound Traffic from AS112 Servers . . . . . . . . . . . . . . 8 6. Inbound Traffic from AS112 Servers . . . . . . . . . . . . . . 8
7. Corrective Measures . . . . . . . . . . . . . . . . . . . . . 9 7. Corrective Measures . . . . . . . . . . . . . . . . . . . . . 9
8. AS112 Contact Information . . . . . . . . . . . . . . . . . . 10 8. AS112 Contact Information . . . . . . . . . . . . . . . . . . 10
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
10. Security Considerations . . . . . . . . . . . . . . . . . . . 12 10. Security Considerations . . . . . . . . . . . . . . . . . . . 12
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13
11.1. Normative References . . . . . . . . . . . . . . . . . . 13 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
11.2. Informative References . . . . . . . . . . . . . . . . . 13 12.1. Normative References . . . . . . . . . . . . . . . . . . 14
Appendix A. Change History . . . . . . . . . . . . . . . . . . . 14 12.2. Informative References . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15 Appendix A. Change History . . . . . . . . . . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16
1. Introduction and Target Audience 1. Introduction and Target Audience
Readers of this document may well have experienced an alarm from a Readers of this document may well have experienced an alarm from a
firewall or an intrusion-detection system, triggered by unexpected firewall or an intrusion-detection system, triggered by unexpected
inbound traffic from the Internet. The traffic probably appeared to inbound traffic from the Internet. The traffic probably appeared to
originate from one of several hosts discussed further below. originate from one of several hosts discussed further below.
The published contacts for those hosts may well have suggested that The published contacts for those hosts may well have suggested that
you consult this document. you consult this document.
skipping to change at page 6, line 18 skipping to change at page 6, line 18
significance. This means that sending queries out to the Internet is significance. This means that sending queries out to the Internet is
not sensible: there is no way for the public DNS to provide a useful not sensible: there is no way for the public DNS to provide a useful
answer to a question which has no global meaning. answer to a question which has no global meaning.
Despite the fact that the public DNS cannot provide answers, many Despite the fact that the public DNS cannot provide answers, many
sites have misconfigurations in the way they connect to the Internet sites have misconfigurations in the way they connect to the Internet
which results in such queries relating to internal infrastructure which results in such queries relating to internal infrastructure
being sent outside the site. From the perspective of the public DNS, being sent outside the site. From the perspective of the public DNS,
these queries are junk -- they cannot be answered usefully and result these queries are junk -- they cannot be answered usefully and result
in unnecessary traffic being received by the nameservers which in unnecessary traffic being received by the nameservers which
underpin the operation of the public DNS (the so-called root servers underpin the operation of the reverse DNS (the so-called reverse
which serve "IN-ADDR.ARPA"). servers [RFC5855] which serve "IN-ADDR.ARPA").
To isolate this traffic, and reduce the load on the rest of the DNS To isolate this traffic, and reduce the load on the rest of the
infrastructure, dedicated servers have been deployed in the Internet reverse DNS infrastructure, dedicated servers have been deployed in
to receive and reply to these junk queries. These servers are the Internet to receive and reply to these junk queries. These
deployed in many places in a loosely-coordinated effort known as the servers are deployed in many places in a loosely-coordinated effort
"AS112 Project". More details about the AS112 Project can be found known as the "AS112 Project". More details about the AS112 Project
at <http://www.as112.net/>. can be found at <http://www.as112.net/>.
5. AS112 Nameservers 5. AS112 Nameservers
The nameservers responsible for answering queries relating to The nameservers responsible for answering queries relating to
private-use addresses are as follows: private-use addresses are as follows:
o PRISONER.IANA.ORG (192.175.48.1) o PRISONER.IANA.ORG (192.175.48.1)
o BLACKHOLE-1.IANA.ORG (192.175.48.6) o BLACKHOLE-1.IANA.ORG (192.175.48.6)
skipping to change at page 13, line 5 skipping to change at page 13, line 5
identify traffic received from AS112 nodes, and to provide background identify traffic received from AS112 nodes, and to provide background
information to allow appropriate measures to be taken in response to information to allow appropriate measures to be taken in response to
it. it.
Hosts should never normally send queries to AS112 servers: queries Hosts should never normally send queries to AS112 servers: queries
relating to private-use addresses should be answered locally within a relating to private-use addresses should be answered locally within a
site. Hosts which send queries to AS112 servers may well leak site. Hosts which send queries to AS112 servers may well leak
information relating to private infrastructure to the public network, information relating to private infrastructure to the public network,
which could represent a security risk. which could represent a security risk.
11. References 11. Acknowledgements
11.1. Normative References The authors wish to acknowledge the assistance of S. Moonesamy in the
preparation of this document.
12. References
12.1. Normative References
[RFC1034] Mockapetris, P., "Domain names - concepts and facilities", [RFC1034] Mockapetris, P., "Domain names - concepts and facilities",
STD 13, RFC 1034, November 1987. STD 13, RFC 1034, November 1987.
[RFC1918] Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and [RFC1918] Rekhter, Y., Moskowitz, R., Karrenberg, D., Groot, G., and
E. Lear, "Address Allocation for Private Internets", E. Lear, "Address Allocation for Private Internets",
BCP 5, RFC 1918, February 1996. BCP 5, RFC 1918, February 1996.
11.2. Informative References 12.2. Informative References
[I-D.ietf-dnsop-as112-ops] [I-D.ietf-dnsop-as112-ops]
Abley, J. and W. Maton, "AS112 Nameserver Operations", Abley, J. and W. Maton, "AS112 Nameserver Operations",
October 2009. October 2009.
[I-D.ietf-dnsop-default-local-zones] [I-D.ietf-dnsop-default-local-zones]
Andrews, M., "Locally-served DNS Zones", Andrews, M., "Locally-served DNS Zones",
draft-ietf-dnsop-default-local-zones-14 (work in draft-ietf-dnsop-default-local-zones-14 (work in
progress), September 2010. progress), September 2010.
[RFC5855] Abley, J. and T. Manderson, "Nameservers for IPv4 and IPv6
Reverse Zones", BCP 155, RFC 5855, May 2010.
Appendix A. Change History Appendix A. Change History
This section to be removed prior to publication. This section to be removed prior to publication.
00 Initial draft, circulated as 00 Initial draft, circulated as
draft-jabley-as112-being-attacked-help-help-00 and reviewed at the draft-jabley-as112-being-attacked-help-help-00 and reviewed at the
DNSOP working group meeting at IETF 66. DNSOP working group meeting at IETF 66.
00 Document adopted by the DNSOP working group and renamed 00 Document adopted by the DNSOP working group and renamed
accordingly. accordingly.
skipping to change at page 15, line 5 skipping to change at page 15, line 33
03 Version number bump at request of dnsop chair. 03 Version number bump at request of dnsop chair.
04 Version number bump at request of dnsop chair. Contact 04 Version number bump at request of dnsop chair. Contact
information section truncated to protect the innocent. Minor, information section truncated to protect the innocent. Minor,
non-substantive wordsmithing. References updated. non-substantive wordsmithing. References updated.
05 Version number bump at request of dnsop chair. References 05 Version number bump at request of dnsop chair. References
updated. updated.
06 Change references to root servers to reverse servers, since IN-
ADDR.ARPA has been re-delegated since this document was first
written. Add acknowledgements section.
Authors' Addresses Authors' Addresses
Joe Abley Joe Abley
ICANN ICANN
4676 Admiralty Way, Suite 330 4676 Admiralty Way, Suite 330
Marina del Rey, CA 90292 Marina del Rey, CA 90292
US US
Phone: +1 519 670 9327 Phone: +1 519 670 9327
Email: joe.abley@icann.org Email: joe.abley@icann.org
 End of changes. 11 change blocks. 
20 lines changed or deleted 33 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/