AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node integrates with the AvantGuard DNSFilter API to update blocked URLs in a DNS filtering system. It allows users to modify existing URL filters by specifying the ID of the blocked URL entry and providing updated details. This is useful for network administrators or security teams who want to dynamically manage which URLs are blocked within their organization's DNS filtering policies.

Practical examples include:

  • Updating a blocked URL filter to change the URL pattern or parameters.
  • Adjusting filtering rules without manually accessing the DNSFilter dashboard.
  • Automating updates to blocked URLs as part of a larger security workflow.

Properties

Name Meaning
Id The unique identifier of the blocked URL entry to update.
Additional Body Fields Optional additional fields to include in the update request body. Currently supports:
- Blocked Url A JSON object representing the URL filter resource to update (e.g., new URL pattern).

Output

The node outputs JSON data representing the response from the AvantGuard DNSFilter API after updating the blocked URL entry. This typically includes confirmation of the update, the updated resource details, or error information if the update failed.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating with the AvantGuard DNSFilter API.
  • The base URL for API requests is https://api.dnsfilter.com.
  • The node uses standard HTTP headers for JSON content (Accept and Content-Type set to application/json).

Troubleshooting

  • Invalid ID: If the provided Id does not correspond to an existing blocked URL entry, the API will likely return an error indicating the resource was not found. Verify the ID before running the node.
  • Malformed JSON in Blocked Url: The Blocked Url field expects valid JSON. Invalid JSON syntax will cause parsing errors. Ensure the JSON is well-formed.
  • Authentication Errors: Missing or invalid API credentials will result in authentication failures. Confirm that the API key credential is correctly configured.
  • API Rate Limits or Network Issues: Temporary failures may occur due to rate limiting or connectivity problems. Retrying after some time or checking network settings can help.

Links and References

Discussion