Setu-TS
    Preparing search index...

    Interface DenoSrvRecord

    One SRV record as Deno.resolveDns returns it.

    The target field is named target here; Node spells the identical field name. Normalizing both onto SrvRecord.host is the whole reason these two resolvers exist separately — a port that passed either shape through unchanged would type-check on both runtimes and produce undefined hostnames on one of them.

    0.2.0

    interface DenoSrvRecord {
        port: number;
        priority: number;
        target: string;
        weight: number;
    }
    Index
    port: number

    TCP port.

    priority: number

    RFC 2782 priority.

    target: string

    Target hostname.

    weight: number

    RFC 2782 weight.