LuaDNS API

Name: LuaDNS API
Brand: LuaDNS API
Availability: InStock

✓ Official Vendor SpecCloud InfrastructureNetworkingbasic12 EndpointsREST

For Agents

Manage DNS zones and records on LuaDNS — list and CRUD zones, list and CRUD records, list DS records for DNSSEC delegation — across 12 endpoints with HTTP Basic auth.

Install Jentic One Beta

Connect the LuaDNS API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the LuaDNS API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with LuaDNS API.

Create, retrieve, update, and delete DNS zones owned by the authenticated user

Create, retrieve, update, and delete records (A, AAAA, MX, TXT, CNAME, etc.) on a zone

List the DS records configured on a zone for DNSSEC delegation to a registrar

GET STARTED

Start building with LuaDNS API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use LuaDNS API for, with concrete tasks.

★ Infrastructure-as-code DNS management

Platform teams check zones and records into a Git repo and reconcile against LuaDNS via API on every deploy. The 12 endpoints are enough to drive a Terraform-style reconciliation loop — diff intended vs actual records, then create, update, or delete to converge. HTTP Basic auth keeps the integration trivial in CI.

GET /zones/{id}/records, diff against the desired set in the repo, and POST, PUT, or DELETE records on the zone to converge.

Automated SSL certificate provisioning

ACME-based certificate issuance (Let's Encrypt, ZeroSSL) needs DNS-01 challenges, which means temporary TXT records on a zone. LuaDNS's record CRUD endpoints support this flow — the certbot helper creates the TXT, validation runs, then the helper deletes it. Because the surface is small, integrating LuaDNS with an ACME client takes under an hour.

POST /zones/{zone_id}/records to create the _acme-challenge TXT record, wait for validation, then DELETE the record by ID.

Failover and traffic-shaping automation

Operations teams use the API to flip A or CNAME records to a backup endpoint when monitoring detects an outage. Because LuaDNS exposes record-update directly, the runbook is a one-call change with low TTL pre-configured for fast propagation. The DS record endpoint supports DNSSEC parity with the registrar after every change.

On a health-check failure, PUT /zones/{zone_id}/records/{id} with the backup IP for the affected A record, then verify by GET /zones/{zone_id}/records.

Agent-driven DNS assistant via Jentic

An AI agent embedded in an SRE chatops bot lets engineers say 'add a TXT record for verification on example.com' and have it applied. The agent calls LuaDNS through Jentic, which holds the Basic-auth credentials in its vault so the engineer never pastes them into chat. The 12-endpoint surface fits comfortably in one tool listing.

Use Jentic to search 'create luadns record', load POST /zones/{zone_id}/records, and execute it with the parsed zone, record type, name, and value from the chat message.

Key Endpoints

12 endpoints — luadns is a managed authoritative dns provider whose rest api exposes the operations needed to run zones programmatically — zone crud, record crud, ds record listing for dnssec delegation, and a user-settings endpoint.

METHOD

PATH

DESCRIPTION

GET

/zones

List all zones

POST

/zones

Create a new zone

GET

/zones/{id}

Get a zone

PUT

/zones/{id}

Update a zone

DELETE

/zones/{id}

Delete a zone

GET

/zones/{zone_id}/records

List records on a zone

POST

/zones/{zone_id}/records

Create a record on a zone

GET

/zones/{zone_id}/ds_records

List DS records for DNSSEC delegation

GET

/zones

List all zones

POST

/zones

Create a new zone

GET

/zones/{id}

Get a zone

PUT

/zones/{id}

Update a zone

DELETE

/zones/{id}

Delete a zone

GET

/zones/{zone_id}/records

List records on a zone

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

LuaDNS Basic-auth credentials (email + API token) are stored encrypted in the Jentic vault. Jentic builds the Basic Authorization header at execution time — the raw token never enters the agent's context, which matters because LuaDNS tokens have full account scope.

Intent-based discovery

Agents search by intent (for example 'create luadns record' or 'list zones') and Jentic returns the matching LuaDNS operation with its input schema, so the agent supplies the zone ID and record values without browsing docs.

Time to first call

Direct LuaDNS integration: a few hours for Basic-auth handling and zone scoping. Through Jentic: under 30 minutes — search, load schema, execute.

FAQs

Specific to using LuaDNS API through Jentic.

What authentication does the LuaDNS API use?

LuaDNS uses HTTP Basic authentication — the email and API token combination from the LuaDNS account dashboard are sent in the Authorization header. Through Jentic, the credentials live in the vault and Jentic constructs the Basic header at execution time, so the agent never holds the raw token.

Can I create DNS records through the LuaDNS API?

Yes. POST /zones/{zone_id}/records creates a record of any supported type (A, AAAA, MX, TXT, CNAME, etc.) on the named zone. Use Jentic search 'create luadns record' to load the operation and supply zone ID, record type, name, content, and TTL.

What are the rate limits for the LuaDNS API?

LuaDNS applies fair-use rate limiting per account and returns HTTP 429 when exceeded. Because most automation flows are bursty (deploy time) rather than sustained, the limit is rarely hit; Jentic surfaces 429 responses unchanged so the agent retries with backoff.

How do I retrieve DS records for DNSSEC delegation through Jentic?

Search Jentic for 'list luadns ds records', load GET /zones/{zone_id}/ds_records, and execute it with the zone ID. The response contains the DS records you copy into the registrar to complete DNSSEC delegation.

Does the LuaDNS API support bulk record imports?

There is no single bulk-import endpoint — instead, iterate POST /zones/{zone_id}/records for each record in the desired set. Most automation tools wrap this in a small loop and use the list endpoint to confirm convergence.

How many endpoints does the LuaDNS API expose?

12 endpoints across zones, records, DS records, and user settings. The full surface fits in a single Jentic operation search and is small enough for an agent to hold in context for a chatops-style DNS workflow.

LuaDNS API

Connect the LuaDNS API to your agent

Capabilities

Start building with LuaDNS API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs