Ikoula VPS API icon

Ikoula VPS API

Interact with Ikoula VPS API. Developed by Ascenzia - www.ascenzia.fr

Overview

This node interacts with the Ikoula VPS API to manage secondary DNS entries for virtual private servers (VPS). Specifically, the "Delete Secondary DNS" operation allows users to remove a secondary DNS entry associated with a given server IP and DNS ID. This is useful in scenarios where you need to clean up or update DNS configurations by removing outdated or incorrect secondary DNS records.

Practical examples include:

  • Automating DNS cleanup when decommissioning VPS instances.
  • Managing DNS entries programmatically as part of infrastructure-as-code workflows.
  • Integrating DNS management into broader VPS lifecycle automation.

Properties

Name Meaning
Subscription ID The VPS subscription ID (number identifying the VPS service).
Server IP The IP address of the server hosting the VPS whose secondary DNS entry is to be deleted.
DNS ID The unique identifier of the secondary DNS entry to delete.
Response Format The format of the API response; options are JSON or XML.

Output

The output is a JSON object representing the API response from the Ikoula VPS service after attempting to delete the specified secondary DNS entry. The structure depends on the API's response format but generally includes confirmation of deletion or error details.

If the response format is set to XML, the raw XML string is returned instead.

No binary data output is produced by this operation.

Example JSON output might look like:

{
  "status": "success",
  "message": "Secondary DNS entry deleted successfully"
}

or, in case of failure:

{
  "status": "error",
  "message": "DNS ID not found"
}

Dependencies

  • Requires an API key credential for authenticating with the Ikoula VPS API.
  • The node uses RSA public key encryption to encrypt the password before sending it to the API.
  • The base URL for the API defaults to https://api.ikoula.com but can be overridden via credentials.
  • Proper network access to the Ikoula API endpoint is necessary.

Troubleshooting

  • No credentials provided!: Ensure that valid API authentication credentials are configured in n8n before running the node.
  • Invalid DNS ID: If the DNS ID does not exist or is incorrect, the API will return an error. Verify the DNS ID corresponds to an existing secondary DNS entry.
  • Server IP mismatch: The server IP must match the VPS instance where the DNS entry exists.
  • API connectivity issues: Network problems or incorrect API URLs can cause request failures. Confirm internet connectivity and correct API endpoint configuration.
  • Response format errors: If XML is selected but downstream nodes expect JSON, parsing errors may occur. Choose the appropriate response format based on your workflow needs.

Links and References

Discussion