Thanks you so much, Mark.
Based on your input, I successfully found the culprit It's one of the LDNS.
It's supposed to config the zone as
"xx.node.epc.mnc{AAA}.mcc{BBB}.3gppnetwork.org". But somehow it's been configed
as "node.epc.mnc{AAA}.mcc{BBB}.3gppnetwork.org", which is not delegated
ved)
> --
>
> -- Original --
> From: "同屋";<39223...@qq.com>;
> Send time: Wednesday, Jan 6, 2021 8:43 PM
> To: "同屋"<39223...@qq.com>; "marka";
> Cc: "Bind-users";
> Subject: re:Re: "not su
Actually, the background is a little bit complicated. In short, the topo is as
belows. dns1 were swapped by a new one (say dns1*), then the issue happened.
After that, we dropped all the request from dns1*, then the issue was gone.
There is no config change during the whole process, no
Thanksmark,butwhythisissueisrelatedtoloadbalancer?
-- Original Message --
From: "Mark Andrews";
Date: 2021-01-06 19:09
To: "同屋"<39223...@qq.com;
To:
"bind-users";
Subject: Re: "not subdomain of zone {XXXX} -- invalid re
Complain to the administrators of the zone. They have not properly delegated
it. We see this often with load balancers.
The zone a.b.example has been delegated but the answer is as if it is from
b.example.
--
Mark Andrews
> On 6 Jan 2021, at 21:02, 同屋 <39223...@qq.com> wrote:
>
>
> The
The version of bind is BIND 9.10.5-P3 id:7d5676f
One day, I found that the size of named.run is increasing very quickly. And a
lot of "invalid response" entries were spotted in the log. Details is as
follows (I replace the sensitive info with {},{AAA} etc.)
DNS format error from {IP}#53
6 matches
Mail list logo
