A specialized webhook provider for ExternalDNS that enables automated record management for Technitium DNS Server.

This project is designed to run exclusively as a sidecar container within the external-dns pod. It implements the ExternalDNS Webhook provider API to bridge Kubernetes resource discovery with Technitium's management API.

Note: You have to either provide TECHNITIUM_USER and TECHNITIUM_PASSWORD or just TECHNITIUM_TOKEN

You can manage these records types. PTR records and the zones will be created and/or deleted (Zones will not be deleted unless all records are gone and TECHNITIUM_DELETE_PTR_ZONE is set to true.)

Setting up Technitium doesn’t have to be a chore. I’ve polished your instructions to make them more professional, readable, and authoritative while keeping that helpful peer-to-peer vibe.

Follow these streamlined steps to configure your users and zones correctly.

Before managing records, you need a user with the appropriate permissions.

1. Navigate: Go to the Administration tab and select the Users sub-tab.
2. Create User: Click to add a new user.

   Note: Ensure the Username and Password contain no spaces. The Display Name is purely cosmetic and can be formatted however you like.

3. Assign Permissions: Add the new user to the DNS Administrators group.
4. Session Management: You may set the Session Timeout to 0 for an indefinite session. However, the application is designed to automatically re-authenticate and refresh the API key before the timeout expires.

The API requires an existing zone to function. Please ensure your target zone is created manually before proceeding.

1. Navigate: Open the Zones tab in the top navigation bar.
2. Initialize: Click the Add Zone button.
3. Select Type: Choose your required zone type.
   • Primary Zone: The standard choice for most setups.
   • Other: Consult your DNS Engineer if your infrastructure requires a Secondary or Forwarding zone.
4. Finalize: Click Add to save the configuration.

To compile the project locally, execute:

make build

To remove build artifacts and clean your workspace:

make clean

If you are contributing to this project, you must first initialize the linting environment:

make lint-init

This command installs all necessary dependencies and tools for code analysis.

Once initialized, you can analyze the codebase by running:

make lint

To verify only the project licenses, use:

make license

To execute the unit testing suite, run:

make test

We welcome all Pull Requests! To ensure a smooth review process, please adhere to the following requirements:

• ✅ Validation: Ensure your changes pass all checks. Running make lint will automatically verify code quality and inject the required license headers into required source files.
• 🧪 Testing: All new functionality must include corresponding unit tests. A successful test pass is required for any merge to the main branch.
• ✍️ Security: The final commit of your PR must be signed (e.g., GPG/SSH) before it can be merged for release.

A huge thank you to the Technitium team for building such a robust, high-performance, and feature-rich open-source DNS server. This project is intended to make integrating their excellent software with Kubernetes seamless and efficient.

Building and maintaining open-source tools takes time and focus. I want to give a special thanks to my wife, my daughter, and my son. Your support and patience allow me the space to be a "geek" and contribute back to the community. You are my greatest motivation!

A special thanks to the external-dns-infoblox-webhook team. This plugin is based on their excellent work—thank you for providing such a solid foundation for the community!

This project is licensed under the Apache License 2.0. See the LICENSE file for details.