Request external whois/geoip services if search in Netbox failed for IP address or prefix #1987

Closed
opened 2025-12-29 17:21:11 +01:00 by adam · 1 comment
Owner

Originally created by @vsvetlov on GitHub (Sep 4, 2018).

Environment

  • Python version: 3.5.4
  • NetBox version: 2.4.4

Proposed Functionality

That is a really convenient feature in some IPAM solutions.
It would be cool to see it in NetBox.
When you search for IP address or IP prefix and there is no such entry in NetBox DB we could request external services for information about IP/Prefix.

Use Case

You can forget about the services like whois and use IPAM to resolve any external and internal IP addresses.

Database Changes

None

External Dependencies

https://ipwhois.readthedocs.io/en/latest/

Originally created by @vsvetlov on GitHub (Sep 4, 2018). <!-- NOTE: This form is only for proposing specific new features or enhancements. If you have a general idea or question, please post to our mailing list instead of opening an issue: https://groups.google.com/forum/#!forum/netbox-discuss NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.5.4 * NetBox version: 2.4.4 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality That is a really convenient feature in some IPAM solutions. It would be cool to see it in NetBox. When you search for IP address or IP prefix and there is no such entry in NetBox DB we could request external services for information about IP/Prefix. <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case You can forget about the services like whois and use IPAM to resolve any external and internal IP addresses. <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes None <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> ### External Dependencies https://ipwhois.readthedocs.io/en/latest/
adam closed this issue 2025-12-29 17:21:11 +01:00
Author
Owner

@jeremystretch commented on GitHub (Sep 5, 2018):

This strikes me as an extraneous feature that's going to be much more work to maintain than it's worth. In general you should already know whether an IP address is part of your assigned space or not, and if not, performing a manual WHOIS lookup is trivial. Additionally, many users run NetBox in an isolated environment, rendering such a feature useless and necessitating the need for yet another configuration option. It's a neat idea, but we have too much in the backlog right now for extra features.

@jeremystretch commented on GitHub (Sep 5, 2018): This strikes me as an extraneous feature that's going to be much more work to maintain than it's worth. In general you should already know whether an IP address is part of your assigned space or not, and if not, performing a manual WHOIS lookup is trivial. Additionally, many users run NetBox in an isolated environment, rendering such a feature useless and necessitating the need for yet another configuration option. It's a neat idea, but we have too much in the backlog right now for extra features.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#1987