Skip to main content
resolveAny - node__dns.d.ts - Node documentation
function resolveAny

Usage in Deno

```typescript import { resolveAny } from "node:node__dns.d.ts"; ```
resolveAny(
hostname: string,
callback: (
err: ErrnoException | null,
addresses: AnyRecord[],
) => void
,
): void
> [!WARNING] Deno compatibility > The `ttl` option is not supported. Uses the DNS protocol to resolve all records (also known as `ANY` or `*` query). The `ret` argument passed to the `callback` function will be an array containing various types of records. Each object has a property `type` that indicates the type of the current record. And depending on the `type`, additional properties will be present on the object: Here is an example of the `ret` object passed to the callback: ```js [ { type: 'A', address: '127.0.0.1', ttl: 299 }, { type: 'CNAME', value: 'example.com' }, { type: 'MX', exchange: 'alt4.aspmx.l.example.com', priority: 50 }, { type: 'NS', value: 'ns1.example.com' }, { type: 'TXT', entries: [ 'v=spf1 include:_spf.example.com ~all' ] }, { type: 'SOA', nsname: 'ns1.example.com', hostmaster: 'admin.example.com', serial: 156696742, refresh: 900, retry: 900, expire: 1800, minttl: 60 } ] ``` DNS server operators may choose not to respond to `ANY` queries. It may be better to call individual methods like [resolve4](../.././node__dns.d.ts/~/resolve4), [resolveMx](../.././node__dns.d.ts/~/resolveMx), and so on. For more details, see [RFC 8482](https://tools.ietf.org/html/rfc8482).

Parameters

hostname: string
callback: (
err: ErrnoException | null,
addresses: AnyRecord[],
) => void

Return Type

void