SLAACsense streamlines the process of configuring DNS records on OPNsense routers using Technitium DNS Server.
Designed to enhance network management, the tool automatically defines DNS A, AAAA, and PTR records for each device connected to the network based on its DHCPv4 hostname.
By leveraging the DHCPv4 lease information and mapping it to the MAC address, the tool navigates the NDP table to retrieve IPv6 addresses associated with each host. Subsequently, it configures the DNS records accordingly, providing a seamless solution for maintaining an up-to-date and accurate DNS configuration.
Define the environment variables in the docker-compose file, then run: docker compose up -d
| Variable Name | Description | Example Value |
|---|---|---|
OPNSENSE_URL |
The base URL of your OPNsense instance | http://192.168.1.1 (required) |
OPNSENSE_API_KEY |
OPNsense API key | your_opnsense_api_key (required) |
OPNSENSE_API_SECRET |
OPNsense API secret | a_very_secret_token (required) |
TECHNITIUM_URL |
The base URL of your Technitium DNS instance | dns.myawesomehome.home.arpa (required) |
TECHNITIUM_TOKEN |
Technitium DNS token | another_very_secret_token (required) |
DNS_ZONE_SUBNETS |
Comma separated DNS zones and IPv4 subnet | 192.168.1.0/24=lan.home.arpa,192.168.2.0/24=dmz.home.arpa (required) |
DO_V4 |
If set to true, A records will be configured, otherwise only AAAA records are configured | false (defaults to false) |
VERIFY_HTTPS |
Verify OPNsense and Technitium's SSL certificates | true (defaults to true) |
CLOCK |
Interval between updates (in seconds) | 30 (defaults to 30) |
You have to create the corresponding DNS zones in the Technitium dashboard, you can configure them as primary or conditional forwarder zones.
I welcome contributions! Feel free to submit issues, feature requests, or pull requests.
For example, you may add the support for other DNS servers, like Bind, and other routing platforms, like pfSense and OpenWrt.
This tool is released under the MIT license. See the LICENSE file for details.