starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

PowerDNS Integration as an app that can be enabled disabled. #2737

New Issue
Closed
opened 2025-12-29 18:21:35 +01:00 by adam · 2 comments
adam commented 2025-12-29 18:21:35 +01:00
Owner
Copy Link

Originally created by @kvedder-amplex on GitHub (Jul 12, 2019).

Environment

  • Python version: 3.6
  • NetBox version: 2.6.0

Proposed Functionality

I work for a small ISP and we are currently in the process of deploying Netbox as our IPAM. We are exploring options for integrating PowerDNS into the ecosystem to be fed by Netbox's data.

I was considering having the team here write a Django app within Netbox that perhaps could be enabled and disabled that would store information about the PowerDNS server's it would communicate with. As changes are made in the IPAM, it could update the database on the DNS servers as needed.

Another option would be to build a separate service that would translate the webhooks into the proper API query to PowerDNS. It could be installed on the IPAM server, but be entirely separate from Netbox.

Its worth noting that we haven't fully flushed out any design yet. I wanted to hear from the community and project leaders as to weather or not this is something that would be acceptable or if it deviated too much from the core functions of the IPAM.

Use Case

One potential use case:
A device is added into Netbox, once added an API call is made to the configured PowerDNS server(s) adding the necessary records.

Database Changes

A new model and template/view would be needed to enable, disable, and configure the integration. Perhaps the webhooks model could be extended to enable some of this functionality.

External Dependencies

I don't envision there being any new dependencies.

Originally created by @kvedder-amplex on GitHub (Jul 12, 2019). ### Environment * Python version: 3.6 * NetBox version: 2.6.0 ### Proposed Functionality I work for a small ISP and we are currently in the process of deploying Netbox as our IPAM. We are exploring options for integrating PowerDNS into the ecosystem to be fed by Netbox's data. I was considering having the team here write a Django app within Netbox that perhaps could be enabled and disabled that would store information about the PowerDNS server's it would communicate with. As changes are made in the IPAM, it could update the database on the DNS servers as needed. Another option would be to build a separate service that would translate the webhooks into the proper API query to PowerDNS. It could be installed on the IPAM server, but be entirely separate from Netbox. Its worth noting that we haven't fully flushed out any design yet. I wanted to hear from the community and project leaders as to weather or not this is something that would be acceptable or if it deviated too much from the core functions of the IPAM. ### Use Case One potential use case: A device is added into Netbox, once added an API call is made to the configured PowerDNS server(s) adding the necessary records. ### Database Changes A new model and template/view would be needed to enable, disable, and configure the integration. Perhaps the webhooks model could be extended to enable some of this functionality. ### External Dependencies I don't envision there being any new dependencies.
adam closed this issue 2025-12-29 18:21:35 +01:00
adam commented 2025-12-29 18:21:35 +01:00
Author
Owner
Copy Link

@lampwins commented on GitHub (Jul 12, 2019):

This is the intended use case for webhooks. Adding this sort of thing to the core of NetBox only serves to create bloat, which in turn creates maintenance overhead for a feature only a subset of the userbase cares about.

@lampwins commented on GitHub (Jul 12, 2019): This is the intended use case for webhooks. Adding this sort of thing to the core of NetBox only serves to create bloat, which in turn creates maintenance overhead for a feature only a subset of the userbase cares about.
adam commented 2025-12-29 18:21:35 +01:00
Author
Owner
Copy Link

@kvedder-amplex commented on GitHub (Jul 12, 2019):

Thanks for the feedback. Looks like we should build the functionality into a separate tool that will translate the webhooks from Netbox into the appropriate calls to the PowerDNS API. Perhaps once complete the code could be added to netbox-community as a separate repository.

@kvedder-amplex commented on GitHub (Jul 12, 2019): Thanks for the feedback. Looks like we should build the functionality into a separate tool that will translate the webhooks from Netbox into the appropriate calls to the PowerDNS API. Perhaps once complete the code could be added to netbox-community as a separate repository.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#2737
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?