Groups | Search | Server Info | Login | Register


Groups > comp.protocols.dns.bind > #16053

Re: Error "Query section mismatch : got"

Path csiph.com!news.uzoreto.com!news.etla.org!nntp-feed.chiark.greenend.org.uk!ewrotcd!usenet-its.stanford.edu!usenet.stanford.edu!not-for-mail
From tale <d.lawrence@salesforce.com>
Newsgroups comp.protocols.dns.bind
Subject Re: Error "Query section mismatch : got"
Date Wed, 19 Aug 2020 10:05:50 -0400
Lines 21
Approved bind-users@lists.isc.org
Message-ID <mailman.807.1597845926.942.bind-users@lists.isc.org> (permalink)
References <CA+N48Xf8vKph42T4xq_KgnwjzpQV1YVboWztm6CmPcMok6_GQA@mail.gmail.com> <20200819114133.GA6272@fantomas.sk> <CAGrdBBuZgP3oR3Q5zJjR6W-p8zB3GD-ggYPp0CFXE6mAdPfYiA@mail.gmail.com>
NNTP-Posting-Host lists.isc.org
Mime-Version 1.0
Content-Type text/plain; charset="UTF-8"
X-Trace usenet.stanford.edu 1597845973 8593 149.20.1.60 (19 Aug 2020 14:06:13 GMT)
X-Complaints-To action@cs.stanford.edu
To bind-users <bind-users@lists.isc.org>
Return-Path <d.lawrence@salesforce.com>
X-Original-To bind-users@lists.isc.org
Delivered-To bind-users@lists.isc.org
DKIM-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=salesforce.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=8bu3j4lCWgTANRtl7E/FFevG3w92WmyypEnXmAeK3tQ=; b=a8/fnbEvHp/CVso6oaAIJT+6tnL2sY3hACjOvnRt8Ggy4hucmzCKSDlxJ1IvRJ86AS zL1kOJoUdNht/WQpI9ZOlJzDqL07dgpL8pho5VW4vNI6n+N5PrZJ2FQ4bMKHb8j/KyaM 3BnOjFaE6uhD5gvWEXdJnKaIQP8LNkqPaVVdE=
X-Google-DKIM-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=8bu3j4lCWgTANRtl7E/FFevG3w92WmyypEnXmAeK3tQ=; b=GVwuBgEcf/c43FBvglCH8kStgBTR1Q4lfIEzkf7R7U67+S7odcYa5YkgzMpsrssfwT RQIro0fhwV5TxuhhFtvcVkPLcriIYD0F9bBwivL2Bjk7H7CjPz8P+Gu1s5T4pyjWT4jj WYiMDxi8OPfTtLp2c341hxGO963M/PAH/AK9PXKWV5ihq8plfT91VV8GCctwqcOKev7P c8hN1Zt2plUuqEaHIoL7golTCoZFSpE4OfOV2EGiapu0EiM/K41Ql+miU8FxeaP85oqK y2dsuaInRvRrS5jIMllbAqMY1Yg1itRdFetVv8o30Ehd+k21eIjQY03H70sOxSWPKk9s SHeA==
X-Gm-Message-State AOAM532OJR1UpAsCjff/PXXJd797/MV/t/iHZSXsQlWc1QAHtgFQgXRY PTsYRQO9w8JtCFtHRFTlEZXa+s7MWcUFYPWrvXEiz3CyLchjrA==
X-Google-Smtp-Source ABdhPJzlfUS78/Dprx8UBZ7CQ5ZENhjDGj2h6e7qL4y86+vYDTImTffmnaWYI65EBDlon1SOeQyYOKEbLpoa/Qbrl7I=
X-Received by 2002:a17:902:968d:: with SMTP id n13mr9987278plp.260.1597845960962; Wed, 19 Aug 2020 07:06:00 -0700 (PDT)
In-Reply-To <20200819114133.GA6272@fantomas.sk>
X-Spam-Status No, score=-0.2 required=5.0 tests=DKIMWL_WL_MED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS autolearn=disabled version=3.4.2
X-Spam-Checker-Version SpamAssassin 3.4.2 (2018-09-13) on mx.pao1.isc.org
X-BeenThere bind-users@lists.isc.org
X-Mailman-Version 2.1.29
Precedence list
List-Id BIND Users Mailing List <bind-users.lists.isc.org>
List-Unsubscribe <https://lists.isc.org/mailman/options/bind-users>, <mailto:bind-users-request@lists.isc.org?subject=unsubscribe>
List-Archive <https://lists.isc.org/pipermail/bind-users/>
List-Post <mailto:bind-users@lists.isc.org>
List-Help <mailto:bind-users-request@lists.isc.org?subject=help>
List-Subscribe <https://lists.isc.org/mailman/listinfo/bind-users>, <mailto:bind-users-request@lists.isc.org?subject=subscribe>
X-Mailman-Original-Message-ID <CAGrdBBuZgP3oR3Q5zJjR6W-p8zB3GD-ggYPp0CFXE6mAdPfYiA@mail.gmail.com>
X-Mailman-Original-References <CA+N48Xf8vKph42T4xq_KgnwjzpQV1YVboWztm6CmPcMok6_GQA@mail.gmail.com> <20200819114133.GA6272@fantomas.sk>
Xref csiph.com comp.protocols.dns.bind:16053

Show key headers only | View raw


On Wed, Aug 19, 2020 at 7:42 AM Matus UHLAR - fantomas
<uhlar@fantomas.sk> wrote:
> again, why you query for 250.0-24.199.212.125.in-addr.arpa
> under normal circumstances there's no point of querying that name.
>

Well yes and no.   While an individual user would typically not,
resolvers sure will.  While trying to resolve
250.199.212.125.in-addr.arpa, it will eventually get to
250.199.212.125.in-addr.arpa CNAME 250.0-24.199.212.125.in-addr.arpa.
 Then it will need to resolve the canonical name, and a response like
the original one that was shown will be clearly buggy.

I say "possibly" because from my vantage, all three of
ns{,1,2}.viettelidc.com.vn, the authorities for
0-24.199.212.125.in-addr.arpa, are giving fine answers right now (on
udp; blocked on tcp).   This includes the originally reported problem
IP, 115.84.177.8

-- 
tale

Back to comp.protocols.dns.bind | Previous | Next | Find similar


Thread

Re: Error "Query section mismatch : got" tale <d.lawrence@salesforce.com> - 2020-08-19 10:05 -0400

csiph-web