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 → Add Secondary DNS
AI-generatedOverview
This node integrates with the Ikoula Dedicated Server API to manage secondary DNS entries for dedicated servers. Specifically, the "Add Secondary DNS" operation allows users to add a new secondary DNS entry associated with a given server IP address.
Common scenarios where this node is beneficial include automating DNS management tasks in server infrastructure workflows, such as dynamically adding secondary DNS records when provisioning or updating dedicated servers. For example, a user can automate the addition of secondary DNS entries after deploying a new server to ensure proper DNS resolution and redundancy.
Properties
| Name | Meaning |
|---|---|
| Server IP | The IP address of the dedicated server on which the secondary DNS entry will be added. |
| DNS Name | The DNS name to assign to the new secondary DNS entry. |
| Response Format | The format of the API response; options are JSON or XML. |
Output
The node outputs the API response from Ikoula as JSON (or XML if selected). The json output field contains the data returned by the API regarding the newly added secondary DNS entry. This typically includes confirmation details such as the DNS entry ID, name, status, and any other metadata provided by the API.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Ikoula API.
- The node uses the Ikoula API endpoint (default:
https://api.ikoula.com) to perform operations. - The password used for authentication is encrypted using RSA public key encryption before sending.
- No additional external dependencies beyond standard HTTP requests and cryptographic functions bundled with the node.
Troubleshooting
- Missing Credentials: If no API credentials are provided, the node throws an error "No credentials provided!". Ensure that valid API authentication credentials are configured in n8n.
- Invalid Server IP or DNS Name: Providing incorrect or malformed server IP addresses or DNS names may cause API errors. Verify input values carefully.
- API Response Errors: The node passes through API error messages. Common issues might include permission errors, invalid parameters, or network connectivity problems. Review the API response message for details.
- Response Format Mismatch: Selecting XML response format requires downstream nodes to handle XML parsing accordingly. If JSON is expected but XML is returned, parsing errors may occur.
Links and References
- Ikoula API Documentation (general reference for API endpoints and parameters)
- n8n Documentation for configuring credentials and using HTTP Request nodes
This summary focuses exclusively on the "DNS Secondary" resource and the "Add Secondary DNS" operation as requested.