AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node interacts with the AvantGuard DNSFilter API to retrieve information about network subnets. Specifically, the "Network Subnets All" operation fetches a list of all network subnets available in the system, optionally filtered by additional query parameters such as an organization ID. This node is useful for network administrators or security professionals who want to programmatically access and manage subnet data within their organization's DNS filtering setup.

Practical examples include:

  • Retrieving all network subnets associated with a specific organization to audit or monitor network segments.
  • Integrating subnet data into automated workflows for network configuration or compliance reporting.

Properties

Name Meaning
Additional Query Parameters Optional fields to refine the request. Currently supports: Organization Id (number) to filter subnets by a specific organization.

Output

The node outputs JSON data representing the list of network subnets retrieved from the API. Each item in the output typically contains details about a subnet, such as its identifier, IP range, associated organization, and other metadata provided by the DNSFilter service.

If binary data were involved, it would be summarized here; however, this node deals exclusively with JSON data.

Dependencies

  • Requires an API key credential for authenticating requests to the AvantGuard DNSFilter API.
  • The base URL for API requests is https://api.dnsfilter.com.
  • The node expects the environment to have internet access to reach the external DNSFilter service.

Troubleshooting

  • Common issues:

    • Authentication failures due to missing or invalid API keys.
    • Network connectivity problems preventing access to the DNSFilter API.
    • Invalid or missing query parameters causing the API to return errors or empty results.
  • Error messages:

    • Unauthorized or 401 errors indicate issues with the API key; verify that the correct credential is configured.
    • 400-series errors may result from malformed query parameters; ensure that the organization ID, if used, is a valid number.
    • Timeout or network errors suggest connectivity issues; check firewall settings and internet access.

Links and References

Discussion