AvantGuard - CIPP icon

AvantGuard - CIPP

AvantGuard - CIPP

Actions136

Overview

This node interacts with the AvantGuard CIPP API to retrieve DNS configuration information using an exec-based DNS resolver. Specifically, it supports the "Retrieve Exec Dns Config" operation under the "List" resource. This operation is useful when you need to programmatically fetch DNS configuration details such as domain-specific resolver settings or selectors, which can be critical for network diagnostics, security configurations, or dynamic DNS management.

Practical examples include:

  • Automating retrieval of DNS resolver configurations for specific domains.
  • Integrating DNS config data into workflows that require dynamic DNS resolution parameters.
  • Auditing or monitoring DNS settings across multiple environments.

Properties

Name Meaning
Action The action parameter specifying the type of DNS config retrieval to perform.
Domain The domain name for which the DNS configuration is being requested.
Resolver The DNS resolver address or identifier to use for the query.
Selector A selector string used to filter or specify particular DNS configuration details.

All properties are required and sent as query parameters in the API request.

Output

The node outputs JSON data containing the DNS configuration retrieved from the AvantGuard CIPP API. The exact structure depends on the API response but generally includes details about the DNS exec configuration related to the specified domain, resolver, and selector.

No binary data output is indicated by the source code or property definitions.

Dependencies

  • Requires an API key credential for authenticating with the AvantGuard CIPP API.
  • Needs the base URL of the AvantGuard resource API configured in credentials.
  • Depends on the @avantguardllc/n8n-openapi-node package and a local OpenAPI specification (openapi.json) for building request properties and handling API communication.

Troubleshooting

  • Missing or invalid API credentials: Ensure the API key and base URL are correctly set in the node's credentials.
  • Invalid or missing required properties: All four properties (Action, Domain, Resolver, Selector) must be provided; otherwise, the API call will fail.
  • Network or connectivity issues: Verify network access to the AvantGuard API endpoint.
  • Unexpected API responses: Check if the domain, resolver, or selector values are valid and supported by the API.

Common error messages would likely relate to authentication failures, invalid query parameters, or network timeouts. Resolving these involves verifying credentials, input correctness, and network status.

Links and References

Discussion