Batch DNS Lookups

Batch DNS Lookups

What it does

Batch DNS Lookups lets you resolve up to 25 hosts in one request and get DNS answers back in a single response. Send a queries array with each item containing a host and an optional type of A, AAAA, MX, NS, TXT, CNAME, or PTR.

Each result includes the queried host, the record type, and a status of OK, NXDOMAIN, NODATA, or ERROR. Depending on the record type, the response may also include addresses for A and AAAA, mx records with preference and exchange, names for NS or CNAME, txt strings, or ptr targets. When a row fails, error is returned for that row.

Use Batch DNS Lookups when you need to verify domains, inspect mail routing, or check reverse DNS at scale. It fits domain onboarding flows, infrastructure audits, and bulk asset checks where you want to reduce resolver round trips and keep DNS results aligned by input row.

curl -X POST "https://api.eu.apyverse.com/apyhub/batch-dns-lookups" \ -H "apy-token: $APY_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "queries": [ { "host": "google.com", "type": "A" } ] }'

About this endpoint

What it does

Performs up to 25 DNS lookups in a single request. You send a list of query objects with a required host and an optional record type, and the response returns a results array with one DNS answer object per query.

Request Body

Parameter	Type	Mandatory	Description
queries	Object Array	Yes	Array of DNS queries to resolve. Max 25 items.
queries[].host	String	Yes	Domain, FQDN, or IP address for PTR lookups.
queries[].type	ENUM	No	Record type to query. Allowed values: `A`, `AAAA`, `MX`, `NS`, `TXT`, `CNAME`, `PTR`. Default: `A`. Omit for `A`.

Response

Returns a JSON object with a data object that contains a results array. Each item in results is a DNS answer object with status, host, and type fields, plus record-specific fields such as addresses, names, mx, ptr, txt, or error depending on the query and result.

Parameter	Type	Mandatory	Description
data	Object	No	Wrapper object containing the response payload.
data.results	Object Array	No	DNS answer objects, one per submitted query.
data.results[].host	String	Yes	Queried host, or IP address when the query type is `PTR`.
data.results[].type	ENUM	Yes	Record type that was queried. Allowed values: `A`, `AAAA`, `MX`, `NS`, `TXT`, `CNAME`, `PTR`.
data.results[].status	ENUM	Yes	Result status. Allowed values: `OK`, `NXDOMAIN`, `NODATA`, `ERROR`.
data.results[].addresses	String Array	No	IPv4 (`A`) or IPv6 (`AAAA`) addresses.
data.results[].names	String Array	No	Hostnames returned for `NS` or `CNAME` queries.
data.results[].mx	Object Array	No	MX resource records. Each item includes `preference` and `exchange`.
data.results[].mx[].preference	Integer	Yes	MX preference; lower values indicate higher priority.
data.results[].mx[].exchange	String	Yes	Mail exchanger hostname, often with a trailing dot.
data.results[].ptr	String Array	No	PTR target names returned for reverse DNS lookups.
data.results[].txt	String Array	No	TXT RDATA strings, one element per TXT record.
data.results[].error	String	No	Present when `status` is `ERROR`; contains the resolver or validation error for that row.

Notes

The request body queries array is limited to 25 items. Only the fields relevant to the queried record type are populated in each result item; other record-specific fields are omitted.

Body

Name

Type

Description

bodyREQUIRED

object

—

What it does

QUICKSTART

Quickstart

What you'll get back

About this endpoint

What it does

Request Body

Response

Notes

Body

Errors any endpoint can return