I was never able to uncover the underlying problem with that update.
The only clue I had was the service remained in "activating" state,
rather than "running". named was listening as expected, was transfering
zone data, was caching and serving the correct data, but didn't seem to
recognize it
> On 27. 1. 2023, at 1:49, John Thurston wrote:
> And now when I study my xfer.log more closely, the behavior changed this
> morning when I completed the update from 9.18.10 -> 9.18.11
> I'm not yet ready to revert, because this isn't affecting my business (this
> is a really small zone). Is a
Hi John.
Personally, I would start by drawing a picture (I like pictures) of all the
players in the game and gathering data, leaving nothing out, including:
- All servers, with all IP addresses.
- SOA and NS records of working zones and the troublesome RPZ zone.
- Which servers are author
I have a primary server and a couple of secondaries. After making
adjustments to my RPZ yesterday (which almost never change), I noticed
an oddity. One of my secondaries is performing gratuitous AXFRs of the
RPZ. This isn't a huge performance issue, as my RPZ is only 7.3KB. I
want to understand
4 matches
Mail list logo
