Reverse NS Lookup

Find all domains using this nameserver

This page lists every .dk domain whose delegation includes the nameserver ns2.nsd.dk, together with its IP addresses, network, zone-transfer and ANY-query behaviour, the protocols and RFCs it supports (TCP, EDNS, cookies, NSID, DNS over TLS/HTTPS …), the nameserver sets it is used in and how fast those sets answer. Use it to size a DNS provider, audit a migration or find domains still pointing at an old server. Data comes from our own scanners, which re-resolve every .dk domain in the zone roughly once a week.

ns2.nsd.dk at a glance#

nameserver profile from our scan data

The nameserver ns2.nsd.dk appears in the delegation of 388 .dk domains in our dataset — 0.03% of every scanned .dk domain. The full list is below — here is how those domains look under the hood.

On the DNSSEC side, 0 (0.0%) validate as secure — below the zone-wide average of 63.9%, while 342 (88.1%) are unsigned, with none failing validation outright — a further 46 come back indeterminate.

One thing worth flagging: 42 of these domains (10.8%) look like lame delegations — the .dk registry still points them here, but this nameserver doesn't answer authoritatively for the zone, which usually means the hosting was cancelled and the delegation was left dangling.

Response time: across 346 timed domains, our resolver needed 76 ms on average to answer an A query and 75 ms for an NS query. Per nameserver set below.

ns2.nsd.dk#

Probed 2026-11-16 21:47
Network
Probes
AXFR Refused
IXFR Refused
Glue 62.242.205.2
ANY Answers
Version 100.100.100

Protocols & RFCs#

probed 2026-11-08 13:10
Protocol / featureStandardSupportedWhat it is
DNS over TCPRFC 7766, RFC 9210YesRequired for every nameserver: large answers, DNSSEC and truncation fall back to TCP.
EDNS(0)RFC 6891Yes UDP buffer 1232Extension mechanism behind DNSSEC, cookies and every other option below.
EDNS version negotiationRFC 6891BADVERS (correct)A query with EDNS version 1 must get BADVERS back.
Unknown EDNS optionsRFC 6891Ignored (correct)An option the server does not know must be ignored, not make the query fail.
DNS cookiesRFC 7873, RFC 9018YesLightweight server cookies against spoofing and amplification.
NSIDRFC 5001NoNames the server instance that answered (useful behind anycast).
TCP keepaliveRFC 7828NoAnnounces how long an idle TCP connection is kept open.
Client subnet (ECS)RFC 7871Understood, not used for this zone (scope /0)Lets the nameserver tailor answers to the client's network (CDNs, geo-DNS).
Extended DNS errorsRFC 8914NoExplains a refusal or failure with an error code, seen on a query outside its zones.
ZONEVERSIONRFC 9660NoReports the zone serial it answered from.
DNS error reportingRFC 9567NoAdvertises a reporting agent resolvers can send failures to.
Refuses recursionRFC 5358YesAn authoritative server should not resolve other people's names for anyone who asks.
DNS over TLS (DoT)RFC 7858, RFC 9539NoEncrypted transport on port 853 (resolver-to-authoritative per RFC 9539).
DNS over HTTPS (DoH)RFC 8484NoEncrypted transport on port 443 (/dns-query). Rare on authoritatives.
DNS over QUIC (DoQ)RFC 9250Not probedOur probe tool cannot speak QUIC yet.

Probed over IPv4 at 62.242.205.2 with questions about bopriis.dk, a zone it serves. Other addresses of an anycast or multi-server setup can differ. AXFR, IXFR and minimal ANY answers (RFC 8482) are in the probe card above. “No” for an encrypted transport means nothing answered on its port while plain DNS did. Zone-wide adoption.

Response time over time#

78 days
0 ms85 ms171 ms256 ms341 ms2026-07-23: median 71 ms, p90 112 ms, 91 scans2026-07-24: median 75 ms, p90 127 ms, 209 scans2026-07-25: median 74 ms, p90 131 ms, 142 scans2026-07-30: median 74 ms, p90 124 ms, 35 scans2026-07-31: median 56 ms, p90 87 ms, 46 scans2026-08-01: median 66 ms, p90 359 ms, 26 scans2026-08-02: median 58 ms, p90 70 ms, 21 scans2026-08-03: median 70 ms, p90 108 ms, 31 scans2026-08-04: median 72 ms, p90 88 ms, 11 scans2026-08-06: median 65 ms, p90 108 ms, 29 scans2026-08-07: median 71 ms, p90 112 ms, 42 scans2026-08-08: median 67 ms, p90 92 ms, 26 scans2026-08-09: median 60 ms, p90 314 ms, 14 scans2026-08-14: median 79 ms, p90 386 ms, 14 scans2026-08-15: median 70 ms, p90 95 ms, 48 scans2026-08-16: median 71 ms, p90 109 ms, 14 scans2026-08-17: median 55 ms, p90 149 ms, 29 scans2026-08-18: median 64 ms, p90 98 ms, 46 scans2026-08-19: median 79 ms, p90 327 ms, 19 scans2026-08-20: median 66 ms, p90 148 ms, 22 scans2026-08-21: median 74 ms, p90 309 ms, 16 scans2026-08-25: median 36 ms, p90 83 ms, 35 scans2026-08-26: median 38 ms, p90 57 ms, 165 scans2026-08-27: median 33 ms, p90 52 ms, 10 scans2026-09-03: median 41 ms, p90 53 ms, 43 scans2026-09-04: median 45 ms, p90 60 ms, 77 scans2026-09-05: median 48 ms, p90 61 ms, 45 scans2026-09-06: median 58 ms, p90 72 ms, 23 scans2026-09-07: median 46 ms, p90 73 ms, 43 scans2026-09-08: median 48 ms, p90 80 ms, 49 scans2026-09-09: median 58 ms, p90 80 ms, 38 scans2026-09-10: median 49 ms, p90 75 ms, 22 scans2026-09-11: median 50 ms, p90 67 ms, 12 scans2026-09-12: median 52 ms, p90 61 ms, 10 scans2026-09-15: median 43 ms, p90 70 ms, 22 scans2026-09-16: median 43 ms, p90 60 ms, 48 scans2026-09-17: median 44 ms, p90 62 ms, 27 scans2026-09-18: median 41 ms, p90 65 ms, 21 scans2026-09-19: median 51 ms, p90 61 ms, 24 scans2026-09-20: median 39 ms, p90 61 ms, 10 scans2026-09-21: median 43 ms, p90 55 ms, 22 scans2026-09-22: median 42 ms, p90 59 ms, 44 scans2026-09-23: median 49 ms, p90 70 ms, 209 scans2026-09-24: median 53 ms, p90 67 ms, 89 scans2026-09-25: median 48 ms, p90 63 ms, 194 scans2026-09-26: median 45 ms, p90 64 ms, 142 scans2026-09-28: median 49 ms, p90 64 ms, 157 scans2026-09-29: median 50 ms, p90 66 ms, 314 scans2026-09-30: median 51 ms, p90 72 ms, 170 scans2026-10-05: median 48 ms, p90 63 ms, 90 scans2026-10-06: median 51 ms, p90 66 ms, 31 scans2026-10-07: median 52 ms, p90 62 ms, 23 scans2026-10-08: median 52 ms, p90 64 ms, 126 scans2026-10-09: median 53 ms, p90 83 ms, 86 scans2026-10-13: median 48 ms, p90 60 ms, 46 scans2026-10-14: median 45 ms, p90 66 ms, 107 scans2026-10-15: median 47 ms, p90 59 ms, 51 scans2026-10-16: median 46 ms, p90 50 ms, 7 scans2026-10-20: median 45 ms, p90 61 ms, 5 scans2026-10-21: median 43 ms, p90 53 ms, 17 scans2026-10-22: median 40 ms, p90 53 ms, 20 scans2026-10-23: median 30 ms, p90 51 ms, 16 scans2026-10-24: median 43 ms, p90 55 ms, 18 scans2026-10-25: median 44 ms, p90 55 ms, 23 scans2026-10-26: median 31 ms, p90 54 ms, 7 scans2026-10-27: median 29 ms, p90 50 ms, 22 scans2026-10-28: median 32 ms, p90 46 ms, 15 scans2026-10-29: median 44 ms, p90 283 ms, 16 scans2026-10-30: median 38 ms, p90 52 ms, 20 scans2026-10-31: median 47 ms, p90 52 ms, 17 scans2026-11-01: median 37 ms, p90 50 ms, 19 scans2026-11-02: median 43 ms, p90 50 ms, 16 scans2026-11-03: median 35 ms, p90 55 ms, 108 scans2026-11-04: median 38 ms, p90 52 ms, 66 scans2026-11-05: median 42 ms, p90 53 ms, 120 scans2026-11-06: median 43 ms, p90 54 ms, 63 scans2026-11-09: median 41 ms, p90 53 ms, 111 scans2026-11-10: median 39 ms, p90 55 ms, 58 scans2026-07-232026-09-192026-11-10

The p90 line is clipped at the top of the chart on its worst days (highest p90 386 ms).

39 ms median on 2026-11-10p90 55 ms58 timed scanssolid: median · dashed: 90th percentile
ScannerDaysTimed scansTypical medianTypical p90
Reference scanner charted2075740 ms53 ms
Scanner 2201,11145 ms60 ms
Scanner 313473100 ms316 ms
Scanner 421365266 ms534 ms

Time our reference scanner needed, through its own resolver, to answer the first A query for .dk domains delegated to ns2.nsd.dk, per calendar day (lame delegations excluded). It includes the resolver and the network path, and the resolver picks the fastest nameserver of each delegation, so it describes the nameserver sets this server appears in rather than this one server. Other scanners sit elsewhere and see different absolute numbers (table above); read the line for changes over time. Days with fewer than 5 timed scans are left out.

Direct round-trip time#

7 days
0 ms13 ms26 ms39 ms52 ms2026-11-10: median 6 ms, p90 13 ms, 5 answers2026-11-11: median 7 ms, p90 240 ms, 8 answers2026-11-12: median 8 ms, p90 255 ms, 8 answers2026-11-13: median 7 ms, p90 227 ms, 8 answers2026-11-14: median 6 ms, p90 232 ms, 8 answers2026-11-15: median 6 ms, p90 229 ms, 8 answers2026-11-16: median 12 ms, p90 244 ms, 7 answers2026-11-102026-11-132026-11-16

The p90 line is clipped at the top of the chart on its worst days (highest p90 255 ms).

12.0 ms median on 2026-11-16p90 244 mssolid: median · dashed: 90th percentile

Answered authoritatively: 52 of 52 queries in the last 30 days.

One SOA query (no recursion, UDP) sent straight to 62.242.205.2 (IPv4) from our reference scanner about every three hours, with no resolver in between: the time is this server's own answer plus the network path from us, unlike the resolver-inclusive response time. Other addresses of an anycast or multi-server setup can differ.

Nameserver sets using ns2.nsd.dk#

top 1 by domains
Nameserver setDomainsAvg response (A)NS lookup
ns.nsd.dk · ns2.nsd.dk 388 76 ms 75 ms

Times are the scanner's own lookups through its resolver on each domain's latest scan, so they include resolver overhead; compare sets with each other rather than reading them as raw authoritative round-trip times.

📈 DNSSEC Status Over Time

Loading…