IETF Logo Mail Archive

Re: [DNSOP] status opcode?

Roy Arends <roy@dnss.ec> Wed, 09 November 2016 13:11 UTC

Return-Path: <roy@dnss.ec>
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 BC88A1296AC for <dnsop@ietfa.amsl.com>; Wed, 9 Nov 2016 05:11:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dnss.ec
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 IX3JGCmhdS_v for <dnsop@ietfa.amsl.com>; Wed, 9 Nov 2016 05:11:51 -0800 (PST)
Received: from mail-yb0-x22e.google.com (mail-yb0-x22e.google.com [IPv6:2607:f8b0:4002:c09::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 516D1129602 for <dnsop@ietf.org>; Wed, 9 Nov 2016 05:11:50 -0800 (PST)
Received: by mail-yb0-x22e.google.com with SMTP id d59so41051016ybi.1 for <dnsop@ietf.org>; Wed, 09 Nov 2016 05:11:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dnss.ec; s=google; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=algZFCp91IBd0GTMPsPAmsnVeOsHgSKVCjY4BZWntZM=; b=GusM579xx7rN13adFQ33Zgb+muI2/jcv/DLQ91HTdubkTR39eVQWW80/jMRtQwoC9S mSD3R19wGoZv8g3aaDqb+qDPid7DZUsqBBZWkMaqapR3YdGGOIUAjdYceM8k4Q+6jhgb 6AjqPC6wtKRK6veVFZhyPhUl73t5eLPEuTXVg=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=algZFCp91IBd0GTMPsPAmsnVeOsHgSKVCjY4BZWntZM=; b=gyZgkjI6f2Kc7QdifZ7q8BHk994icmFAMrd/sn52SknRhxS1DdsDxeV8sjRIbqOAPV hbQ1oSSIGnZIpoJbGb3fHYFbwHii6By1JD/nVFNslhts6rVUe4Ii2nc7ZsZSv7ov4KMB IYOEYAsjSqdpJCXi6LORGwWp+ZcmFoY65xcu3JmsMsvwsb7SXAhGfSKHey48z+zGccDN HTbXJUIz3LgFMB6oj7pV88T965JfNC2TRewyG0gbo9qaXEB3zS973e0pkyZmgLhmqg/4 1vorRmM37dq3/Cclb5ZW3kCWZxnevMjajTirIUuQX7B3VGNxoL8xCvhBJfROJOkDtbou vALQ==
X-Gm-Message-State: ABUngvc7ndhb4GtcUFfbG/gquXSBPBDCa9BU08qRP5/6hpIs7Bl1/nydvcoe53bQSzErtg==
X-Received: by 10.37.211.204 with SMTP id e195mr16144931ybf.174.1478697109349; Wed, 09 Nov 2016 05:11:49 -0800 (PST)
Received: from [192.168.1.82] (host217-42-113-167.range217-42.btcentralplus.com. [217.42.113.167]) by smtp.gmail.com with ESMTPSA id n66sm12482517ywe.21.2016.11.09.05.11.48 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 09 Nov 2016 05:11:48 -0800 (PST)
From: Roy Arends <roy@dnss.ec>
Message-Id: <5436F9FD-6AD7-4A5E-B1C5-D71C05006F72@dnss.ec>
Content-Type: multipart/alternative; boundary="Apple-Mail=_75A56711-CDF6-4DC5-B2B4-231E557ED2AB"
Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\))
Date: Wed, 09 Nov 2016 13:11:46 +0000
In-Reply-To: <09AE92A3-FE49-47CC-A52F-6334DD64D810@powerdns.com>
To: Peter van Dijk <peter.van.dijk@powerdns.com>
References: <20161012193813.vkyhvumdjdsufyj2@mycre.ws> <09AE92A3-FE49-47CC-A52F-6334DD64D810@powerdns.com>
X-Mailer: Apple Mail (2.3251)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/ia4X7dKDNQReY_bCEfz9jVl1wgo>
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] status opcode?
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 09 Nov 2016 13:11:52 -0000

> On 9 Nov 2016, at 12:01, Peter van Dijk <peter.van.dijk@powerdns.com> wrote:
> 
> Hello Robert,
> 
> On 12 Oct 2016, at 21:38, Robert Edmonds wrote:
> 
>> What are status queries? Were they ever defined? Are they obsolete?
> 
> I have been unable to find a definition, and I tried quite hard earlier this year when a customer complained we were not handling them! Some VOIP equipment that shall remain unnamed needed to do ENUM queries, but only after a successful ‘health check’.
> 
> The health check looked like this (sorry, don’t have the pcap handy, just this summary):
> ID 0
> flags all zero except for the rcode=2
> all counts zero
> 6 trailing NUL bytes
> 
> Once pdns_server started responding NOTIMP, instead of dropping the query, the equipment was happy.

Argus system and network monitoring software [1] sends DNS status requests.

If you look at [2], it states:

"UDP/DNS sends a 'status-query', UDP/DNSQ sends an 'IN ANY' query. some DNS servers (notably djbdns) do not handle 'status' queries.”

On the wire, it is an apparently random identifier, that doesn’t change between queries and only contains a 12 byte DNS header, opcode 2, rcode 0, all bits and counters 0.

Hope this helps

Warmly,

Roy

[1] http://argus.tcp4me.com/ <http://argus.tcp4me.com/>
[2] http://argus.tcp4me.com/services.html <http://argus.tcp4me.com/services.html>

v2.23.0 | Report a Bug | By Email