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

Integration with PHPIPam #38

New Issue
Closed
opened 2025-12-29 15:30:19 +01:00 by adam · 2 comments
adam commented 2025-12-29 15:30:19 +01:00
Owner
Copy Link

Originally created by @x-zeroflux-x on GitHub (Jun 28, 2016).

Hi There,

We use phpipam for all our ip / vlan / dns management.

It would be great if we could link the systems together so we can provision from netbox and have it talk back to phpipam to link both systems together.

This would allow for the following to take place as an example;

  1. Create customer in rack space
  2. Assign device to rack space.
  3. Allocate IP / Subnet / Vlan to device which makes a call back to phpipam API
  4. Phpipam then allocates the subnet and it has connections from there to manage DNS so it would if setup like ours will auto provision PTR records etc for that device.

A scenario like this would allow for primary management to be handled by netbox rather than phpipam with netbox having more control and functionality other than being (for how we are using it) an asset system at the moment.

Fantastic what you have done - really great project :)

Regards
Shaun

Originally created by @x-zeroflux-x on GitHub (Jun 28, 2016). Hi There, We use phpipam for all our ip / vlan / dns management. It would be great if we could link the systems together so we can provision from netbox and have it talk back to phpipam to link both systems together. This would allow for the following to take place as an example; 1. Create customer in rack space 2. Assign device to rack space. 3. Allocate IP / Subnet / Vlan to device which makes a call back to phpipam API 4. Phpipam then allocates the subnet and it has connections from there to manage DNS so it would if setup like ours will auto provision PTR records etc for that device. A scenario like this would allow for primary management to be handled by netbox rather than phpipam with netbox having more control and functionality other than being (for how we are using it) an asset system at the moment. Fantastic what you have done - really great project :) Regards Shaun
adam closed this issue 2025-12-29 15:30:19 +01:00
adam commented 2025-12-29 15:30:20 +01:00
Author
Owner
Copy Link

@bellwood commented on GitHub (Jun 28, 2016):

IMHO I think extending Netbox to API your DNS would be much better than two systems with similar data.

We use PHPIPAM right now and while I find it flexible, it's not very polished or complete enough a solution for an ISP/DC.

The only thing that is has going for it is custom fields, but, it's turned the schema into a nightmare with everyone crowbarring every little thing into it

@bellwood commented on GitHub (Jun 28, 2016): IMHO I think extending Netbox to API your DNS would be much better than two systems with similar data. We use PHPIPAM right now and while I find it flexible, it's not very polished or complete enough a solution for an ISP/DC. The only thing that is has going for it is custom fields, but, it's turned the schema into a nightmare with everyone crowbarring every little thing into it
adam commented 2025-12-29 15:30:21 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 28, 2016):

Personally, I would advise strongly against running NetBox and phpIPAM in parallel. Redundant data never ends well. There's also a good chance we'll extend NetBox to support DNS records in manner similar to phpIPAM in the near future.

I'm going to close this issue in favor of the more generic #81 request for webhooks.

@jeremystretch commented on GitHub (Jun 28, 2016): Personally, I would advise strongly against running NetBox and phpIPAM in parallel. Redundant data never ends well. There's also a good chance we'll extend NetBox to support DNS records in manner similar to phpIPAM in the near future. I'm going to close this issue in favor of the more generic #81 request for webhooks.
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#38
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?