> For the complete documentation index, see [llms.txt](https://docs.ambersignals.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ambersignals.com/tutorials/monitoring-dns-records.md).

# Monitoring DNS Records

## Introduction

In the vast landscape of internet security, monitoring Domain Name System (DNS) records is a critical aspect that is often overlooked. DNS, the system that translates human-friendly domain names (like [www.example.com](http://www.example.com/)) into IP addresses that computers use to identify each other on the network, is fundamental to the functioning of the internet. Because of its foundational role, DNS can also be a vector for various security threats if not properly monitored and managed. Here’s how you can monitor them.

## Setup DNS Monitoring

Login to our [dashboard](https://ambersignals.com/dashboard) and click on `DNS Records` to create a new service.

<figure><img src="/files/byNIAtqiW1cBtFdTOhjO" alt=""><figcaption><p>Create DNS Monitoring Service</p></figcaption></figure>

Add a **description** that you remember what this service is for. The **address** is the dns name you want to monitor and the **Record Type** is which dns records you want to monitor and finally the **notification channel** how you want to get notified.

The most common types to monitor are **A, AAAA, CNAME** and **TXT** records. We do recommend to monitor **NS** records as well, because it will easily tell you if your domain was fully taken over or not.


---

# 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:

```
GET https://docs.ambersignals.com/tutorials/monitoring-dns-records.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.