Reverse NS Lookup

Find all domains using this nameserver

This page lists every .dk domain whose delegation includes the nameserver gdns1.interlink.or.jp, 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.

gdns1.interlink.or.jp#

Probed 2026-10-31 23:13
Network
Probes
AXFR Refused
IXFR Refused
Glue N/A
ANY REFUSED
Version unknown

Protocols & RFCs#

probed 2026-11-08 23:31
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 9018NoLightweight server cookies against spoofing and amplification.
NSIDRFC 5001NoNames the server instance that answered (useful behind anycast).
TCP keepaliveRFC 7828YesAnnounces 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 8914YesExplains 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 203.141.128.80 with questions about zamst.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.

Direct round-trip time#

9 days
0 ms74 ms148 ms222 ms296 ms2026-11-10: median 269 ms, p90 274 ms, 4 answers2026-11-11: median 269 ms, p90 274 ms, 8 answers2026-11-12: median 269 ms, p90 274 ms, 8 answers2026-11-13: median 273 ms, p90 274 ms, 8 answers2026-11-14: median 269 ms, p90 274 ms, 8 answers2026-11-15: median 269 ms, p90 274 ms, 8 answers2026-11-16: median 269 ms, p90 274 ms, 8 answers2026-11-17: median 273 ms, p90 274 ms, 8 answers2026-11-18: median 273 ms, p90 274 ms, 5 answers2026-11-102026-11-142026-11-18
273 ms median on 2026-11-18p90 274 mssolid: median · dashed: 90th percentile

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

One SOA query (no recursion, UDP) sent straight to 203.141.128.80 (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.

📈 DNSSEC Status Over Time

Loading…