Hi Don,
Yes.
If you want actual names to look at, these zones are both present on
the same servers:
1.f.1.0.8.a.b.0.1.0.0.2.ip6.arpa
8.f.0.f.1.f.1.0.8.a.b.0.1.0.0.2.ip6.arpa
However, the presence of 8.f.0.f.1.f.1.0.8.a.b.0.1.0.0.2.ip6.arpa is
a mistake and in the mean time someone has c
Hi,
I'm running:
9.16.44-Debian (Extended Support Version)
If I have zones example.com and sub.example.com both loaded, but
example.com contains a record:
sub.example.com. NS elsewhere.example.com.
(i.e. the subzone is delegated to some other server)
is it normal and expected that a query fo
Hi,
I've just started using a catalog zone to tell my secondary servers
to pick up new zones. This is on Debian stable so package version
1:9.16.37-1~deb11u1.
I'd like to stop them from sending notifies when they transfer in a
zone. Neither "notify no;" nor "notify primary-only;" seems to do
it.
Hi Bob,
On Fri, Nov 18, 2022 at 07:20:22AM -0500, Bob McDonald wrote:
> The size of the TCP packets is a problem. You might also look at
> minimal-responses.
The issue seems to be that an SOA query response for this DNSSEC-signed
zone is 2293 bytes, and PowerDNS can not yet retry that SOA query o
On Fri, Nov 18, 2022 at 01:14:27AM +, Andy Smith wrote:
> What happens is that a NOTIFY is sent out, PowerDNS sees it and queries
> for SOA and logs this:
>
> Nov 18 00:25:26 daiquiri pdns_server[32452]: While checking domain freshness:
> Query to '2001:ba8:1f1:f085::53
On Fri, Nov 18, 2022 at 01:14:27AM +, Andy Smith wrote:
> Attached is empty-soa.txt, the text dump of the pcap of 4 packets. It
> shows:
Really attached now…
No. Time SourceDestination Protocol
Length Info
1 0.00 85.119.
Hi,
I recently upgraded a Debian 9 / bind9 system to Debian 11, so that
would be package version 1:9.10.3.dfsg.P4-12.3+deb9u12 to
1:9.16.27-1~deb11u1. Ever since doing so, one particular zone is unable
to be transferred to any of the several PowerDNS secondary servers.
What happens is that a NOTI
I’m having some problems when BIND 9.9.1 on Windows is restarted – it seems to
be unable to load any NSEC3 zones using inline-signing that were working prior
to the restart.
It seems to be working fine for NSEC zones, which leads me to think I’m missing
a configuration step somewhere.
The zon
8 matches
Mail list logo