This is an old style referral like you would have got out of BIND4
where the referral appears in the answer section. Note AA is NOT
set so it is not a valid answer to the question.
% dig +norec ns ok.contact @fwd3.dccdns.com
; <<>> DiG 9.15.4 <<>> +norec ns ok.contact @fwd3.dccdns.com
;; global
On Mon, Jul 5, 2021 at 8:20 PM Mark Andrews wrote:
> This is an error with the delegation of ok.contact. The NS records at the
> delegation point do
> not match those at the zone apex.
I'm curious if this is a re-purposing of the existing "non-improving
referral" message. I totally get how tha
In such case, just don’t do it. The option was meant was early deployments
where IPv6 would be utterly broken. This isn’t a case anymore.
FTR the option is now a separate plugin that needs to be loaded first. But as I
said, just don’t do that, it’s not needed.
Ondrej
--
Ondřej Surý — ISC (He/Hi
First, I subscribe to digest so I hope my reply does the right thing and ends up in the thread, apologies otherwise.
Rick,
It isn't a critical thing and maybe I am overthinking it, but I want to avoid situations down the road where dual-homed systems target the DNS and prefer the IPv6 reply, wh
Hi Team,
Any clue why this? and I my BIND has stopped resolving
07-Jul-2021 15:59:34.588 client @0x7f1c50b7ea88 192.168.10.174#56213 (
cisco.com): query failed (broken trust chain) for cisco.com/IN/A at
query.c:7376
07-Jul-2021 15:59:34.844 client @0x7f1c5d9135a8 192.168.10.174#56214 (
cisco.com)
On 2021 Jul 05, at 18:20, Mark Andrews wrote:
> On 6 Jul 2021, at 06:40, @lbutlr wrote:
>> DNS format error from 64.70.78.82#53 resolving ok.contact/NS for
>> 127.0.0.1#16749: non-improving referra
>
> This is an error with the delegation of ok.contact. The NS records at the
> delegation poin
6 matches
Mail list logo
