> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/connectivity/de/konfiguration/add-cellular-gateway-to-command/set-up-dynamic-dns-for-cellular-gateways.md).

# Dynamic DNS für Cellular Gateways einrichten

Erfahren Sie, wie Sie Dynamic DNS auf einem Verkada Cellular Gateway konfigurieren

Mobilfunk-Gateways können als Site-to-Site-IPsec-IKEv2-VPN-Client fungieren. Die öffentliche IP-Adresse eines VPN-Clients ist erforderlich, um den IPsec-Tunnel einzurichten. Durch das Einrichten von Dynamic DNS wird sichergestellt, dass der VPN-Server immer Zugriff auf die dynamisch zugewiesene öffentliche IP-Adresse des VPN-Clients hat (GC31/GC31-E).

***

## Dynamic DNS auf einem Mobilfunk-Gateway konfigurieren

{% stepper %}
{% step %}
**Gehen Sie in Verkada Command zu Alle Produkte > Gateways.**
{% endstep %}

{% step %}
**Wählen Sie das Gateway aus, das Sie konfigurieren möchten.**
{% endstep %}

{% step %}
**Klicken Sie oben rechts auf Einstellungen.**
{% endstep %}

{% step %}
**Aktivieren Sie unter Netzwerk > Dynamic DNS den Schalter Aktivieren.**

<div align="left" data-with-frame="true"><img src="https://1971509114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiAGnzScvko5PkG7YBy3i%2Fuploads%2Fgit-blob-a2fc0a479b035ede54ea377cd52a043d66797c1c%2Faccdd2fb66b72827a08d0269ff026c870393a7e2.png?alt=media" alt="" width="561"></div>
{% endstep %}

{% step %}
**Wählen Sie den Dienst für Ihr Dynamic DNS aus.**

<div align="left" data-with-frame="true"><img src="https://1971509114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiAGnzScvko5PkG7YBy3i%2Fuploads%2Fgit-blob-30b6e270458c57d57060a231fc025ca08ca92dd8%2F725776de09661bb4336f85942c41850c93fd68cc.png?alt=media" alt="" width="563"></div>
{% endstep %}

{% step %}
**(Optional) Geben Sie den Hostnamen, Benutzernamen, das Passwort und den Server ein.**

<div align="left" data-with-frame="true"><img src="https://1971509114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiAGnzScvko5PkG7YBy3i%2Fuploads%2Fgit-blob-a8c21dead73bb60cd410d22ae2011a736b100f98%2F1c6296f11753ad03ea25c706cec5a365d31e0798.png?alt=media" alt="" width="563"></div>
{% endstep %}

{% step %}
**Klicken Sie auf Übernehmen und dann auf Bestätigen, um Ihre Änderungen zu speichern.**

<div align="left" data-with-frame="true"><img src="https://1971509114-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiAGnzScvko5PkG7YBy3i%2Fuploads%2Fgit-blob-22cae0e1dd39b890e34793fd7eb9769037c59a74%2F0b9ddaf8384dd177af67ea912bc9378a9341184a.png?alt=media" alt=""></div>
{% endstep %}
{% endstepper %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.verkada.com/connectivity/de/konfiguration/add-cellular-gateway-to-command/set-up-dynamic-dns-for-cellular-gateways.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.