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>
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"
To: bind-users <bind-users@lists.isc.org>
In-Reply-To: <20200819114133.GA6272@fantomas.sk>
Precedence: list
Xref: csiph.com comp.protocols.dns.bind:16053

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