- DigiCert product docs
- DigiCert DNS
- Monitor DNS activity
- DNS audit logs
DNS audit logs
The audit log records activity in DigiCert® DNS, including changes to DNS configuration and user login events. Use it to review when an event occurred, which object was affected, who performed the action, and the recorded changes.
Explore the Audit log page
To view audit events, go to Overview > Audit log.
The page displays the following information:
Column | Description |
|---|---|
Change time (GMT) | The date and time recorded for the event |
Change object | The object affected by the event |
Parent object | The containing or related parent object, when recorded |
Object type | The category of object involved, such as User, Zone, TXT, SOA, or Web forward |
Change type | The recorded action, such as Login, Add, Modify, Update, or Delete |
User | The user or API actor associated with the action |
Comment | Additional context recorded with the event, when provided |
Use Filter to narrow the displayed events and the pagination controls to browse the results.
To review an event:
Locate the event in the audit log.
Select its Change time (GMT) link.
Review the Overview and Changes sections in the Audit event panel.
Audit events and details
An audit event identifies an action and the object involved. Events include configuration changes and activities such as user logins, so not every event represents a change to DNS data.
The Audit event panel brings together the event’s timestamp, affected object, object type, change type, actor, and any recorded parent object. It also includes:
Field | Description |
|---|---|
Client IP | The client IP address recorded for the action |
Change comment | Additional context supplied with the action |
Changes | The resources and previous and new values recorded for the event |
Read the Object type and Change type together to understand the event. For example, User with Login describes a login event, while TXT with Add describes the addition of a TXT record.
The details available depend on the event. Review the recorded information rather than assuming every event includes a value comparison.
Audit log timestamps
The Change time (GMT) field shows the event’s date and time in GMT. Use this timestamp when comparing audit events with reported issues or other logs.
When working with logs recorded in a different time zone, account for the time-zone difference before comparing events.
An audit timestamp identifies the recorded action time. It does not establish when every DNS client began receiving an updated response.
Users and API actors
The User field identifies the actor associated with the event. This can be a named user, an API-associated identity, or DigiCert® Support acting on a user’s behalf.
API activity can display a [REST API] prefix in the User column. Review this identity alongside the Client IP, affected object, and change details when investigating automated changes.
When DigiCert® Support impersonates a user, the User field displays Support user (jane.doe), using the impersonated account’s username. Hover over the entry to see Changes made as Jane Doe. This identifies actions performed by DigiCert® Support on the user’s behalf.
The actor and affected object are separate pieces of information. For example, when an account is changed, Change object identifies the affected account, while User identifies the actor associated with the action.
For information about user identities and access, see DNS users. For accounts used by automated processes, see DNS service users.
Change objects and parent objects
The Change object identifies what the event affected. The Parent object provides its containing or related context when that information is recorded.
Field | How to use it |
|---|---|
Change object | Identify the specific object involved in the event |
Parent object | Identify the object’s broader context, when provided |
Object type | Determine what kind of object the name represents |
Use these fields together when similar names appear in multiple events. A blank parent-object value or a dash indicates that no parent object is shown for that event.
For background on zones and their records, see Manage DNS zones.
Previous and new values
The Changes section displays the recorded differences for an event.
Column | Description |
|---|---|
Resource | The field or resource involved in the change |
Previous | The value recorded before the change |
New | The value recorded after the change |
For example, an address change could appear as:
Resource | Previous | New |
|---|---|---|
IPv4 address |
|
|
This comparison helps you identify the specific value that changed, rather than relying only on a general change type such as Modify or Update.
Review the affected object and resource together before interpreting the values. For information about IPv4 address records, see A records.
Audit comments
Audit comments provide context for an action, such as the reason for a change or a related change request reference.
Where an operation provides a Comment field, enter context that will help someone reviewing the event later. For example: Updated the endpoint for the scheduled migration.
The audit log displays recorded comments in the Comment column and as Change comment in the event details. A comment may be absent when none was supplied.