[DNSOP] BCP 231, RFC 8906 on A Common Operational Problem in DNS Servers: Failure to Communicate
rfc-editor@rfc-editor.org Tue, 22 September 2020 17:52 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 151D33A0800; Tue, 22 Sep 2020 10:52:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gYKSMVB1bE1s; Tue, 22 Sep 2020 10:52:27 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7FF123A1999; Tue, 22 Sep 2020 10:52:00 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id E3192F40784; Tue, 22 Sep 2020 10:51:52 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, dnsop@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20200922175152.E3192F40784@rfc-editor.org>
Date: Tue, 22 Sep 2020 10:51:52 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/N5zKv-oZJCb-oiLWqu8z9o8q_Uw>
Subject: [DNSOP] BCP 231, RFC 8906 on A Common Operational Problem in DNS Servers: Failure to Communicate
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Sep 2020 17:52:29 -0000
A new Request for Comments is now available in online RFC libraries.
BCP 231
RFC 8906
Title: A Common Operational Problem in
DNS Servers: Failure to Communicate
Author: M. Andrews, R. Bellis
Status: Best Current Practice
Stream: IETF
Date: September 2020
Mailbox: marka@isc.org,
ray@isc.org
Pages: 24
See Also: BCP 231
I-D Tag: draft-ietf-dnsop-no-response-issue-23.txt
URL: https://www.rfc-editor.org/info/rfc8906
DOI: 10.17487/RFC8906
The DNS is a query/response protocol. Failing to respond to queries,
or responding incorrectly, causes both immediate operational problems
and long-term problems with protocol development.
This document identifies a number of common kinds of queries to which
some servers either fail to respond or respond incorrectly. This
document also suggests procedures for zone operators to apply to
identify and remediate the problem.
The document does not look at the DNS data itself, just the structure
of the responses.
This document is a product of the Domain Name System Operations Working Group of the IETF.
BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements. Distribution of this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC