Re: Updated Docker images (9.18, 9.20, 9.21) - now based on Alpine Linux

2024-08-27 Thread Michael Dahlberg
On Tuesday, August 27th, 2024 at 4:21 AM, Ondřej Surý wrote: > the Docker images have been updated to use Alpine Linux as the base image > and the bind9 binaries are now compiled from the source while building the > Docker images. This is more in-line with the expected Docker (Podman) > workfl

Subdomain DNSSEC

2017-08-28 Thread Michael Dahlberg
My apologies if this question has an easily discoverable answer but my google-fu seems to be failing me today. If a domain is signed, is it possible to delegate a subdomain to a 3rd party who is unable to sign that subdomain? For example, I own example.com and its signed. I'd like to delegate s

Re: Bind Queries log file format

2017-02-03 Thread Michael Dahlberg
On Fri, Feb 3, 2017 at 11:45 AM, Mukund Sivaraman wrote: > > > We may move it to the end of the log message (bugs ticket #44606 has > been created for looking at it). Maybe its location was poor.. please > can everyone who participated in this thread say whether having it at > the end will be ok?

Re: Bind Queries log file format

2017-02-02 Thread Michael Dahlberg
.On Thu, Feb 2, 2017 at 2:24 PM, Paul Roberts wrote: > I agree, there are an awful lot of systems and SIEM products that process > querylogs. This one change will require a huge amount of re-engineering > work in customer environments. > > Exactly Mukund: We use Splunk to analyze the querylogs

Re: Bind Queries log file format

2017-01-25 Thread Michael Dahlberg
On Wed, Jan 25, 2017 at 8:51 AM, Mukund Sivaraman wrote: > > > Rememeber that not only users, but even us developers have to look at > your logs when you send them to us. > > When things are fine, the sun is shining, hay is growing.. all's fine, > and the fields in the log format that a user want

Bind Queries log file format

2017-01-24 Thread Michael Dahlberg
In upgrading from BIND 9.10 to 9.11, it looks as if the query log file format has changed slightly: Previously (9.10 variant) the entry looked something like this: 04-Nov-2016 10:34:03.991 queries: info: client 172.20.10.48#38997 (36.2.20.172.in-addr.arpa): query: 36.2.20.172.in-addr.arpa IN PTR