> For the complete documentation index, see [llms.txt](https://help.glpi-project.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.glpi-project.org/documentation/modules/management/tabs/domains_records.md).

# Domains records

## Domains records

![List of attached records](/files/AgO7BQkcUcXFGwf16Qn8)

## The different tabs

### Impact Analysis

[Impact analysis](/documentation/modules/configuration/general/impact_analysis.md) enables an infrastructure diagram to be drawn up, showing the dependencies and impacts in the event of equipment loss. This can be saved and exported

### Records

A Record object stores all record types that can be found in a DNS zone or DNS configuration file: TXT, A, PTR, SDA, CNAME...

This object must be associated to a Domain object.

You can add an existing record (in Link a record field) or create a new one.

* To add a new record, click on **+Add**
* Enter the differents fields
  * Name
  * Record type
  * Technician in charge
  * Group in charge
  * Creation date
  * TTL
  * Data
* Click on **+Add**

{% hint style="info" %}
Record types are not limited to the default ones and can be customized using drop-down management.
{% endhint %}

### Tickets

View all [tickets](https://github.com/glpi-network/gitbook/blob/main/manual/modules/management/tabs/broken-reference/README.md) linked to the computer

### Problems

This tab refers to all hardware-related [problems](/documentation/modules/assistance/problems.md). Problems can also be linked to tickets, projects, etc. This allows you to have a complete scenario when necessary.

### Documents

The [document](/documentation/modules/management/documents.md) tab lets you link different types of file to a material (PDF, txt, png, etc.) You can attach a document already uploaded to GLPI or add a new one directly from this tab.

### Links

[Links](/documentation/modules/configuration/external_links.md) offer several possibilities. Send the GLPI object file to another URL of your choice, or generate an RDP file, for example.

### Note

The [Notes](/documentation/modules/tabs/notes.md) tab provides a free text field for storing additional information. Notes are displayed in the order of their creation. You can also add a document

## History

The *History* tab is used to show any changes made to an item. The following information about the changes is available:

* ID of the change.
* Date and time the change was made.
* User who made the change. If this field is not filled, it means that the action was done automatically (For example: automatic inventory update).
* Field that was changed.
* Description of the change that was made.

The description of the change represents either the difference between the old and the new value (For example with location field: Change HQ to Remote Office A), or the explanation of the action which was carried out (For example: Uninstallation of a software: "Gimp 2.0").

{% hint style="info" %}
For dropdowns or objects with a parent/child relationship, the modification of a child will appear in the history of the parent element.
{% endhint %}

## All Information

For an item, all information is displayed on one page from the *All* tab. This shows all of the tabs of an object's form in one view, one below the other.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.glpi-project.org/documentation/modules/management/tabs/domains_records.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.