> For the complete documentation index, see [llms.txt](https://docs.glesys.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.glesys.com/products/connectivity/domains-and-dns/how-tos/dynamic-dns-in-pfsense.md).
# Dynamic DNS in pfSense
***
pfSense is a popular firewall built on open‑source software. One of our customers has written an add‑on that lets you easily use pfSense to update your records in our DNS service dynamically.
To enable pfSense to update your DNS entries automatically, you first need to create an API key in the Glesys Cloud control panel. The key must have access to "Domains", and you must allow your IP address to use it.
If you don’t know your IP address, you can set it to `0.0.0.0/0`. We recommend creating a dedicated API key that you use solely for DNS updates.
You configure dynamic DNS updates under **Services → Dynamic DNS** in pfSense.
Under **Service type,** select **GleSYS**.
* For **Hostname**, enter the **record ID** of the DNS entry; you can obtain this by using the `list_records` function in our API.
* **Username** is your API user (typically your CL account).
* **Password** is your API key.
Click **Save and Force Update**.
If you’ve done everything correctly, your IP address will now be added to the DNS record you selected.
---
# 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://docs.glesys.com/products/connectivity/domains-and-dns/how-tos/dynamic-dns-in-pfsense.md?ask=&goal=
```
`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.