Actions32
- Automatic Power Control Actions
- Dedicated Server Actions
- DNS Secondary Actions
- Network Boot Actions
- Network Diagnostic Actions
- Remote Access Control Actions
- Reset Actions
- Reverse DN Actions
- Security Scan Actions
DNS Secondary → List Secondary DNS
AI-generatedOverview
This node interacts with the Ikoula Dedicated Server API to manage secondary DNS entries among other server-related operations. Specifically, the "List Secondary DNS" operation under the "DNS Secondary" resource retrieves a list of secondary DNS entries configured for a given dedicated server identified by its IP address.
Common scenarios where this node is beneficial include:
- Automating the retrieval of secondary DNS configurations for monitoring or auditing purposes.
- Integrating secondary DNS data into workflows that manage DNS settings or synchronize DNS records.
- Fetching DNS secondary entries as part of broader server management automation.
Practical example:
- A user wants to periodically fetch and log all secondary DNS entries for a dedicated server to ensure DNS redundancy is correctly configured.
Properties
| Name | Meaning |
|---|---|
| Server IP | The IP address of the dedicated server for which to list secondary DNS entries. |
| Response Format | The format in which the API response should be returned. Options: JSON, XML. |
Output
The node outputs an array of items, each containing a json field with the API response data. For the "List Secondary DNS" operation, the json field contains the list of secondary DNS entries associated with the specified server IP.
If the response format is JSON, the output will be parsed JSON data representing the secondary DNS entries. If XML is chosen, the raw XML string is returned inside the json.data property.
No binary data output is produced by this operation.
Dependencies
- Requires valid credentials for the Ikoula API, including an email, password, and optionally a custom API URL (defaults to
https://api.ikoula.com). - The password is encrypted using RSA public key encryption before being sent.
- The node makes HTTP requests to the Ikoula API endpoints.
- No additional external dependencies beyond standard n8n credential and HTTP request mechanisms.
Troubleshooting
No credentials provided!
This error occurs if the node is executed without proper Ikoula API credentials configured. Ensure that the API authentication details are set up correctly in n8n credentials.API request failures
Network issues, incorrect server IP, or invalid parameters can cause API errors. Verify the server IP is correct and reachable, and that the API credentials have sufficient permissions.Unexpected response format
If the response format is set to XML but downstream nodes expect JSON, parsing errors may occur. Choose the response format according to your workflow needs.Continue on Fail
If enabled, the node will return error messages in the output instead of stopping execution, allowing workflows to handle errors gracefully.
Links and References
- Ikoula API Documentation (general reference for API endpoints and usage)
- n8n Documentation - Creating Nodes (for understanding node development concepts)