On Tue, 2017-11-28 at 18:25 +0100, Michael Ströder wrote:
>
> Depends on the frontend. If it lets the user impersonate as personal
> user account on the DB connection you get the real who.
Yes, it would be nice. Always depends on the goals of the author.
Thanks again.
>
> It would be nice if
Dirk Bartley wrote:
> You could log the who of who is logged into the database, but if the database
> connection is done from a front end, it would always be the users the front
> end
> connects to the database as. But if you have a front end, just manage it by
> who
> is logged into the Front e
On Tue, 2017-11-28 at 17:10 +0100, Michael Ströder wrote:
> How do you plan to maintain the data?
>
> E.g. if you're using LDAP server as backend *and* you're going to
> maintain the data via LDAP it more boils down how to audit write
> operations on the LDAP server. And this depends on the featu
Thank you for the quick reply!
On Tue, 2017-11-28 at 16:10 +, Brian Candler wrote:
> On 28/11/2017 16:02, Dirk Bartley wrote:
> >
> > One of the features being
> > requested is the ability to log the who, what and when of all changes
> > to the data that dns is serving.
>
> My first inclinat
On 28/11/2017 16:02, Dirk Bartley wrote:
One of the features being
requested is the ability to log the who, what and when of all changes
to the data that dns is serving.
My first inclination would be to use a SQL backend, and put triggers on
the tables to record all insert/update/delete operat
Dirk Bartley wrote:
> I have been asked to look at some options for assisting my employer to
> alter the way our internal dns is served. One of the features being
> requested is the ability to log the who, what and when of all changes
> to the data that dns is serving. Of course when I search for
Greetings
I have been asked to look at some options for assisting my employer to
alter the way our internal dns is served. One of the features being
requested is the ability to log the who, what and when of all changes
to the data that dns is serving. Of course when I search for change
logging,
