draft-ietf-dnsop-no-response-issue-17.txt   draft-ietf-dnsop-no-response-issue-18.txt 
Network Working Group M. Andrews Network Working Group M. Andrews
Internet-Draft R. Bellis Internet-Draft R. Bellis
Intended status: Best Current Practice ISC Intended status: Best Current Practice ISC
Expires: September 12, 2020 March 11, 2020 Expires: September 23, 2020 March 22, 2020
A Common Operational Problem in DNS Servers - Failure To Communicate. A Common Operational Problem in DNS Servers - Failure To Communicate
draft-ietf-dnsop-no-response-issue-17 draft-ietf-dnsop-no-response-issue-18
Abstract Abstract
The DNS is a query / response protocol. Failing to respond to The DNS is a query / response protocol. Failing to respond to
queries, or responding incorrectly, causes both immediate operational queries, or responding incorrectly, causes both immediate operational
problems and long term problems with protocol development. problems and long term problems with protocol development.
This document identifies a number of common kinds of queries to which This document identifies a number of common kinds of queries to which
some servers either fail to respond or else respond incorrectly. some servers either fail to respond or else respond incorrectly.
This document also suggests procedures for zone operators to apply to This document also suggests procedures for zone operators to apply to
skipping to change at page 1, line 40 skipping to change at page 1, line 40
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 12, 2020. This Internet-Draft will expire on September 23, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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 23, line 25 skipping to change at page 23, line 25
is not already known, the following methods of communication could be is not already known, the following methods of communication could be
considered: considered:
o the RNAME of the zone authoritative for the name of the o the RNAME of the zone authoritative for the name of the
misbehaving server misbehaving server
o the RNAME of zones for which the offending server is authoritative o the RNAME of zones for which the offending server is authoritative
o administrative or technical contacts listed in the registration o administrative or technical contacts listed in the registration
information for the parent domain of the name of the misbehaving information for the parent domain of the name of the misbehaving
server, or for zones for which the name server is authoritative server, or for zones for which the name server is authoritative
o the registrar or registry for such zones o the registrar or registry for such zones
o DNS-specific operational fora (e.g. mailing lists) o DNS-specific operational fora (e.g. mailing lists)
Operators of parent zones may wish to regularly test the Operators of parent zones may wish to regularly test the
authoritative name servers of their child zones. However, parent authoritative name servers of their child zones. However, parent
operators can have widely varying capabilities in terms of operators can have widely varying capabilities in terms of
notification or remediation depending on whether they have a direct notification or remediation depending on whether they have a direct
relationship with the child operator. Many TLD registries, for relationship with the child operator. Many TLD registries, for
 End of changes. 4 change blocks. 
5 lines changed or deleted 5 lines changed or added

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