Good points, thanks.
-Original Message-
From: Reindl Harald
To: bind-users@lists.isc.org
Sent: Mon, Apr 18, 2022 12:41 am
Subject: Re: Bind and systemd-resolved
Am 18.04.22 um 07:26 schrieb Leroy Tennison via bind-users:
> When I attempt “dig -t AXFR office.example.com -k
> Kexample_
Thanks, had looked at 'man dig' but had assumed (oops) that only the items
listed under the various OPTIONS headings were available in .digrc. Glad to
learn that @ can also be used (confirmed with testing).
-Original Message-
From: Ondřej Surý
To: Leroy Tennison
Cc: bind-users@lists.
Do you know what a windows DNS admin needs to do to fix that?
On 04/18/2022 5:12 pm, Mark Andrews wrote:
The parent servers are configured to allow recursion (ra) and rather
than returning referrals that are returning
answers provided it is cached.
Also it is pointless to use NSEC3 in the reve
The parent servers are configured to allow recursion (ra) and rather than
returning referrals that are returning
answers provided it is cached.
Also it is pointless to use NSEC3 in the reverse trees as they contain too much
structure.
To find
4.b.3.2.b.1.e.f.f.f.5.b.3.e.a.7.0.1.0.0.0.0.0.0.b.d
Mark Andrews wrote:
> Unless you are pointing recursive clients directly at your
> authoritative servers there is no need. The recursive servers will
> lookup the CNAME target themselves. Additionally recursive servers just
> process the CNAME and ignore the rest of the response
There are a lot of extraneous details in here. This is not a BIND problem.
On Mon, 18 Apr 2022, Leroy Tennison via bind-users wrote:
When I attempt “dig -t AXFR office.example.com -k Kexample_dns.+157+18424.key”
on the DNS server (Bind 9.11) sudoed to root I get:
Why do you need to be root?
Ok, thanks for the confirmation (no recursive clients are pointing to
this server, it's only used as an authoritative server).
Le lun. 18 avr. 2022 à 10:08, Mark Andrews a écrit :
>
> Unless you are pointing recursive clients directly at your authoritative
> servers there is no need. The recursi
Unless you are pointing recursive clients directly at your authoritative
servers there is no need. The recursive servers will lookup the CNAME target
themselves. Additionally recursive servers just process the CNAME and ignore
the rest of the response to prevent cache poisoning if there is more
Hello,
I recently upgraded from Debian Buster to Debian Bullseye and I'm
having a hard time having the same behavior as before with the new
bind9 version.
Here is my setup :
- I have two DNS domain (domain A.com and domain Z.com) for which my
server is authoritative (as a slave in this case),
- A
9 matches
Mail list logo
