This page lists every .dk domain whose delegation includes the nameserver ns2.domainteam.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.
The nameserver ns2.domainteam.dk appears in the delegation of 805 .dk domains in our dataset — 0.06% 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 64.0%, while 610 (75.8%) are unsigned, with none failing validation outright — a further 195 come back indeterminate.
One thing worth flagging: 195 of these domains (24.2%) 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 610 timed domains, our resolver needed 95 ms on average to answer an A query and 68 ms for an NS query. Per nameserver set below.
Not profiled: it did not answer authoritatively for the zones we asked it about. Retried every few days.
| Nameserver set | Domains | Avg response (A) | NS lookup |
|---|---|---|---|
| ns.domainteam.dk · ns2.domainteam.dk | 800 | 95 ms | 68 ms |
| ns.domainteam.dk · ns2.domainteam.dk · ns3.domainteam.dk | 5 | 49 ms | 48 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.
Loading…