DNS
What does the DNS cluster cover?
AdminKit groups this topic into the DNS cluster: DNS turns domain names into the IP addresses, mail servers and records your tools actually look up — most "it broke" reports trace back to one wrong, missing or not-yet-propagated DNS record somewhere in that chain. AdminKit's DNS tools cover lookups, propagation, DNSSEC and reverse DNS so you can see which record or resolver is actually out of date before you guess.
Tools (10)
All tools →- DNS lookup A, AAAA, MX, TXT, NS, CAA and more for any domain.
- MX lookup Mail exchanger records and their priorities for a domain.
- Reverse DNS (PTR) Resolve an IP address back to its hostname.
- Whois / RDAP Registrar, registration dates, status and nameservers for a domain or IP.
- DNS resolver / leak test Find which DNS resolver your connection is really using, step by step.
- DNSSEC check Live secure / insecure / bogus DNSSEC verdict for any domain.
- DNS propagation check See whether Cloudflare, Google, Quad9 and OpenDNS resolvers agree on a domain's records yet.
- CAA record generator Build CAA DNS records from authorized CAs, wildcard CAs and an iodef address, entirely client-side.
- IDN homograph check: lookalike domains Punycode and Unicode forms of a domain, with mixed-script and confusable-character flags — client-side.
- PTR record generator Compute the in-addr.arpa/ip6.arpa reverse-DNS name for an IP, or decode an arpa name back to its IP, entirely client-side.
Guides (36)
All guides →- DNS Answers That Differ Between Resolvers | AdminKit
- DNS Propagation and TTL Explained | AdminKit Guide
- DNSSEC Explained: What It Actually Protects | AdminKit Guide
- DoH vs DoT: DNS-Privacy Tradeoffs | AdminKit Guide
- What Happens When a Domain Expires? | AdminKit Guide
- Dynamic IP vs CGNAT vs Static: Why It Matters | AdminKit
- Glue Records and Lame Delegation Explained | AdminKit Guide
- Set Up AdminKit's Home Assistant Add-on | AdminKit Guide
- How to Read a DNS Lookup Result | AdminKit Guide
- How to Read a Reverse DNS PTR Lookup Result | AdminKit
- How to Read a WHOIS/RDAP Lookup Result | AdminKit Guide
- How to Read an SVCB/HTTPS DNS Record | AdminKit Guide
- Subdomain Delegation NS/Glue Mismatch Guide | AdminKit
- Protective DNS for Small Business | AdminKit Guide
- Subnet and CIDR Basics Explained | AdminKit Guide
- Using a Subnet Calculator to Plan VLANs | AdminKit
- Point OpenWrt at AdminKit Protective DNS | AdminKit Guide
- Lookalike Domains and IDN Homograph Attacks
- ALIAS, ANAME and CNAME Flattening at the Apex | AdminKit
- What Is DNS Rebinding? | AdminKit Guide
- Find a Dangling CNAME Subdomain Takeover Risk | AdminKit
- How to File an Abuse Report from a WHOIS Result | AdminKit
- How to Read a MAC Vendor Lookup Result | AdminKit Guide
- IPv6 SLAAC and EUI-64 Addressing Explained | AdminKit Guide
- Is My Router's DNS Hijacked? | AdminKit Guide
- Is Your DNS Resolver an Open Resolver? | AdminKit
- Randomized and Locally-Administered MAC Addresses | AdminKit
- PTR Records and Reverse DNS for Mail Servers | AdminKit
- Protective DNS for UK Small Businesses | AdminKit Guide
- Finding an Abuse Contact in a WHOIS/RDAP Result | AdminKit
- What Is an SOA Record? | AdminKit Guide
- Reverse DNS for Investigating an Unfamiliar IP | AdminKit
- How to Verify Crawler User-Agent Claims | AdminKit Guide
- What Is a DNS Zone Transfer (AXFR)? | AdminKit Guide
- What Your IP Lookup Result Actually Shows | AdminKit
- What Are CAA Records? | AdminKit Guide
Glossary (56)
Full glossary →- A record — An A record is the basic DNS record type that maps a hostname to an IPv4 address, defined in RFC 1035. A domain can publish several for the same name to spread traffic across servers. AdminKit's DNS lookup tool queries a domain's A records alongside AAAA, MX, TXT, NS and CAA in one lookup.
- AAAA record — An AAAA record maps a hostname to an IPv6 address, the job an A record does for IPv4, defined in RFC 3596. A dual-stack domain publishes both, letting a resolver pick whichever address family the path supports. AdminKit's DNS lookup tool queries AAAA alongside A, MX, TXT, NS and CAA, so a missing AAAA record is easy to spot.
- Authoritative nameserver — An authoritative nameserver holds a DNS zone's actual source-of-truth records and is the server a recursive resolver ultimately queries for an answer it doesn't already have cached. AdminKit's whois tool looks up which nameservers a domain's registrar has on file, so you can confirm they match what you intentionally configured.
- CAA record — A CAA (Certification Authority Authorization) record is a DNS entry naming which certificate authorities may issue TLS certificates for a domain; without one, any publicly trusted CA can issue if it passes that CA's own validation. AdminKit's DNS lookup tool checks a domain's records, including CAA.
- CDS/CDNSKEY record — A CDS or CDNSKEY record, defined in RFC 7344, lets a DNSSEC-signed domain automate updating the DS record its parent zone publishes, instead of a human copying a key fingerprint into a registrar panel by hand. AdminKit's DNSSEC guide covers the stale-DS-record failure this automation exists to prevent.
- CNAME record — A CNAME record, defined in RFC 1035, is a DNS entry that makes one domain name an alias for another, telling resolvers to look up the target name instead of returning an address directly. AdminKit's DNS lookup tool resolves CNAME records alongside A, MX, TXT and other record types.
- DNS — DNS (the Domain Name System) is the internet's directory service, translating domain names like adminkit.net into the numeric IP addresses computers use to route traffic, by walking a hierarchy of root, top-level-domain and authoritative nameservers. AdminKit's DNS lookup tool shows any domain's current records in one place.
- DNS cookies — DNS cookies, defined in RFC 7873, are an optional EDNS0 extension letting a resolver and authoritative server exchange a token proving a UDP reply isn't spoofed, without the overhead of a full TCP handshake. AdminKit's router DNS-hijack guide covers this as one signal behind detecting a tampered resolver.
- DNS forwarder — A DNS forwarder, defined in RFC 8499, is a nameserver that hands queries to another nameserver instead of walking the authoritative chain itself -- the common setup on home routers and small-office networks. AdminKit's guide to a hijacked router explains how to confirm which upstream resolver a device's forwarder is actually sending queries to.
- DNS NOTIFY — DNS NOTIFY, defined in RFC 1996, lets a zone's primary nameserver immediately tell its secondaries the zone changed, instead of every secondary waiting out the SOA record's refresh timer to notice. AdminKit's zone-transfer guide explains what a secondary actually does once a NOTIFY message wakes it up.
- DNS propagation / TTL — TTL is the number of seconds a DNS resolver is allowed to cache a record before checking again; "propagation" is the real-world delay before every resolver that cached an old answer has that cache expire and fetch the new one. AdminKit's DNS resolver test shows what a fresh resolver currently returns for a domain.
- DNS UPDATE (Dynamic DNS Update) — DNS UPDATE lets an authorized client add, delete or change individual records in a zone directly, without editing and reloading a zone file, and is normally restricted with TSIG or SIG(0) authentication. AdminKit's DNS Lookup tool shows a record's current live value, the same value an authorized or unauthorized Update actually changes.
- DNS64 — DNS64, defined in RFC 6147, lets an IPv6-only client reach an IPv4-only destination by synthesizing an IPv6 address from the destination's A record when no AAAA record exists, for a paired NAT64 translator to route. AdminKit's IPv6 guide covers how transition techniques like DNS64 change what a home network can reach.
- DNSBL — A DNSBL (DNS-based Blackhole List) is a blocklist of IP addresses observed sending spam or abuse, published in a format mail servers can query with ordinary DNS lookups before accepting a message. AdminKit's guide explains why an IP ends up on a blacklist like Spamhaus and how to get delisted.
- DNSKEY record — A DNSKEY record, defined in RFC 4034, publishes the public key a zone uses to sign its own DNS records under DNSSEC, which a validating resolver fetches to verify the zone's RRSIG signatures. AdminKit's DNSSEC guide covers confirming a domain publishes the DS, DNSKEY and RRSIG records a resolver needs.
- DNSSEC — DNSSEC adds cryptographic signatures to DNS records so a validating resolver can confirm a response really came from a domain's authoritative owner and was not forged or altered in transit. AdminKit's DNS Lookup tool shows a domain's DNSKEY, RRSIG and DS records that make up its DNSSEC chain.
- DoH — DoH (DNS over HTTPS), defined in RFC 8484, sends DNS queries inside an encrypted HTTPS connection instead of plain UDP/TCP port 53, so an ISP or attacker on the network can't read or tamper with which domains are being looked up. AdminKit's DNS resolver test walks you through checking which resolver a connection is actually using.
- DoQ (DNS-over-QUIC) — DoQ (DNS-over-QUIC), defined in RFC 9250, encrypts DNS queries using QUIC instead of TLS-over-TCP or HTTPS, avoiding the head-of-line blocking a single stalled connection can cause. AdminKit's DoH-vs-DoT guide compares DoQ's QUIC transport against those encrypted DNS alternatives and their privacy tradeoffs.
- DoT — DoT (DNS over TLS) encrypts DNS queries and responses over a dedicated TLS connection, usually on port 853, keeping DNS traffic separate from ordinary HTTPS traffic rather than blending into it like DoH does. AdminKit's DNS resolver test walks you through checking which resolver your connection actually uses.
- DS record — A DS (Delegation Signer) record is a DNSSEC record a parent zone publishes holding a hash of a child zone's signing key, letting a resolver confirm the delegation is genuine. Defined in RFC 4034 and RFC 4035, it links a chain of trust from the DNS root down. AdminKit's DNS lookup tool shows a domain's DNSSEC chain, DS record included.
- EDNS Client Subnet (ECS) — EDNS Client Subnet (ECS), an EDNS0 option defined in RFC 7871, lets a recursive resolver forward part of a querying client's IP address to an authoritative server so it can return a geographically closer answer. AdminKit's guide to resolver-dependent DNS answers covers ECS as one of the ordinary, non-broken reasons a domain resolves differently.
- EDNS(0) Padding — EDNS(0) Padding, defined in RFC 7830, adds extra bytes to a DNS message so its size alone doesn't reveal which query it carries, closing a side channel encryption leaves open over DoH, DoT or DoQ. AdminKit's DoH-vs-DoT guide covers the encrypted transports padding is meant to be used alongside.
- EDNS0 (Extension Mechanism for DNS) — EDNS0 (RFC 6891) extends DNS with an optional OPT record so resolvers can signal larger payload sizes and other capabilities the original 1987 protocol never anticipated, including DNS Cookies (RFC 7873) and padding. AdminKit's DNS lookup tool sends EDNS0-aware queries so it can retrieve full DNSSEC and large-answer responses correctly.
- Extended DNS Error (EDE) — Extended DNS Error (EDE), an EDNS0 option defined in RFC 8914, lets a DNS server attach a machine-readable code explaining why it answered the way it did, instead of a bare SERVFAIL or NXDOMAIN. AdminKit's DNS lookup tool shows the answers an EDE code would explain, turning an opaque failure into a reason an administrator can act on.
- FQDN — A fully qualified domain name (FQDN) specifies a host's exact position in the DNS hierarchy, from the host down to the root, per the naming rules RFC 1035 defines. Resolution reads each label right to left starting at the DNS root servers. AdminKit's DNS lookup tool validates the FQDN you enter before forwarding the query to its upstream resolver.
- Glue record — A glue record is an A or AAAA record a parent zone publishes alongside an NS delegation, giving a nameserver's IP address directly and avoiding the circular lookup an in-domain nameserver would otherwise need. RFC 7719 formally defines the term. AdminKit's DNS lookup tool helps spot a missing or mismatched glue record at the registrar.
- Homograph Attack — A homograph attack registers or links to a domain whose characters look identical to a trusted one but come from a different script, such as Cyrillic 'а' in place of Latin 'a', so a victim reads the fake as genuine. AdminKit's IDN homograph check shows a domain's Punycode and Unicode forms and flags mixed scripts and confusable characters.
- IXFR (Incremental Zone Transfer) — IXFR, defined in RFC 1995, lets a secondary nameserver pull only the records that changed since its last transfer, instead of re-pulling the whole zone the way AXFR does. DNS NOTIFY (RFC 1996) is what normally prompts that check. AdminKit's zone-transfer guide covers the full AXFR transfer IXFR is a smaller, cheaper alternative to.
- mDNS — mDNS (Multicast DNS) lets devices on a local network resolve each other's .local names without a central DNS server, which is how Bonjour, AirPrint and many smart-home devices find printers and speakers nearby. AdminKit's guide explains why local-network discovery protocols like mDNS still need a firewall at the edge.
- MX record — An MX record is a DNS entry that tells other mail servers which server is responsible for receiving email on behalf of a domain, ordered by a priority value so backups can be listed. AdminKit's MX Lookup tool looks up a domain's MX records directly, in priority order.
- Negative caching — Negative caching lets a resolver remember that a DNS query returned no answer -- NXDOMAIN or an empty NOERROR -- for a TTL set by the zone's SOA record, per RFC 2308. AdminKit's TTL guide explains how that same SOA minimum controls DNS propagation delay.
- NS record — An NS record identifies which servers are authoritative for a domain, holding its actual DNS records and answering queries about it, as distinct from servers that merely cache or forward answers. AdminKit's DNS Lookup tool looks up a domain's NS records to confirm they match at the registrar and in the zone.
- NSEC record — NSEC, defined in RFC 4034 and RFC 4035, is the original DNSSEC record that proves a DNS name genuinely doesn't exist by naming the next real owner name in the zone -- which also lets anyone walk the chain and enumerate it. AdminKit's DNSSEC guide covers the signature chain NSEC plugs into.
- NSEC3 record — NSEC3, defined in RFC 5155, is a DNSSEC record that proves a DNS name doesn't exist using a salted hash of the zone's real owner names, closing the zone-enumeration gap the original NSEC record left open. AdminKit's DNSSEC guide covers where this authenticated denial fits in the signature chain.
- NXDOMAIN — NXDOMAIN is the DNS response code, defined in RFC 1035, a server returns when a queried domain doesn't exist at all, distinct from an empty NOERROR answer meaning the name exists but lacks that record type. AdminKit's negative caching entry explains how resolvers cache an NXDOMAIN answer using the zone's SOA minimum TTL.
- Oblivious DoH (ODoH) — Oblivious DoH (ODoH), defined in RFC 9230, adds a proxy between a DNS client and a DoH resolver (RFC 8484) so the resolver sees an encrypted query but not the client's IP address, and the proxy sees the client's IP but not the query. AdminKit's guide to DoH vs. DoT privacy tradeoffs covers where ODoH fits.
- Open DNS resolver — An open DNS resolver answers recursive queries from any client on the internet rather than only its intended users, letting an attacker spoof a victim's address and trigger a flood of replies far larger than the request -- a DNS amplification attack. AdminKit's resolver test walks you through finding the resolver actually answering a device's queries.
- PTR record — A PTR record is the reverse of an ordinary DNS lookup: it resolves an IP address back to a hostname, stored under the special in-addr.arpa or ip6.arpa zones. AdminKit's Reverse DNS tool looks up a PTR record directly, which mail servers also check before accepting a connection.
- Punycode (internationalized domain names) — Punycode, defined in RFC 3492, is the ASCII encoding that lets internationalized domain names with non-ASCII characters work inside the DNS, converting a label like café.example into xn--caf-dma.example under the hood. AdminKit's WHOIS tool resolves both the Unicode and xn-- forms of a domain when looking up registration data.
- QNAME minimization — QNAME minimization, specified in RFC 7816 and its 2021 update RFC 9156, limits how much of a query name a recursive resolver reveals to each server it asks, instead of sending the full domain name to the root and TLD servers too. AdminKit's DNS privacy guide weighs this resolver-side technique alongside DoH and DoT.
- RDAP — RDAP (Registration Data Access Protocol) is the IETF-standardized successor to WHOIS, returning who registered a domain or IP address block as structured JSON over HTTPS instead of WHOIS's loosely defined plain text. AdminKit's Whois tool looks up domain and IP registration data using the registries' current services.
- Recursive resolver — A recursive resolver is the DNS server a client actually asks, tracking an answer down through the root, TLD and authoritative servers on the client's behalf, then caching it -- the behavior RFC 1034 and RFC 1035 define. AdminKit's resolver test walks you through finding which recursive resolver a connection is actually using.
- RRSIG record — An RRSIG record, defined in RFC 4034, carries the DNSSEC signature over a specific set of DNS records, letting a validating resolver confirm nothing was altered since the zone owner signed it. AdminKit's DNSSEC guide explains how one expired RRSIG signature can take an otherwise-unchanged zone offline for validating resolvers.
- SOA record — An SOA record is the first record in every DNS zone, naming the zone's primary nameserver, administrator contact, and timing values that control how secondary nameservers replicate it. AdminKit's DNS Lookup tool shows a domain's SOA record alongside its other DNS records in one check.
- SRV record — An SRV record publishes the hostname and port a specific service is reachable on for a domain, letting a client discover where to connect for something like SIP or XMPP without one fixed port. AdminKit's LAN discovery guide covers the related mDNS-based pattern that layers SRV-style records on top of multicast DNS.
- Stub resolver — A stub resolver is the lightweight DNS client built into an operating system that forwards every lookup to a recursive resolver rather than walking the DNS hierarchy itself, a pattern RFC 1123 explicitly describes. AdminKit's DNS resolver test walks you through checking which resolver a device's stub resolver is actually using.
- SVCB/HTTPS record — SVCB and HTTPS, both defined in RFC 9460, are DNS record types that publish service-connection hints -- such as supported ALPN protocols or a non-default port -- in the same answer as a service's address. AdminKit's DNS lookup tool shows a domain's full record set, SVCB/HTTPS included.
- TLD (top-level domain) — A top-level domain (TLD) is the last label in a domain name, such as .com or a country code like .uk, delegated under ICANN's registry system per RFC 1591 and published in IANA's root zone. AdminKit's WHOIS tool looks up registration data for a domain under any TLD.
- TSIG (Transaction Signature) — TSIG, defined in RFC 8945, authenticates a DNS message using a secret key shared between two servers, rather than trusting the message based on where it came from, by attaching a keyed hash over its contents plus a timestamp. It's the cryptographic alternative to IP-based allow-listing for zone transfers, which AdminKit's AXFR guide covers from the other side.
- TXT Character-String — A TXT character-string is the basic unit of a DNS TXT record's data: one length octet followed by up to 255 octets of text, as RFC 1035 defines, so longer values like DKIM keys must be split across several strings in one record. AdminKit's TXT record splitter cuts a long value into correctly quoted 255-octet character-strings.
- TXT record — A TXT record is a DNS entry that holds arbitrary text, originally meant for human-readable notes but now used almost entirely to carry machine-readable policy strings other systems parse automatically, such as the SPF policy AdminKit's SPF check tool reads directly from a domain's TXT record. A domain can publish several unrelated TXT records at once.
- Typosquatting — Typosquatting is registering a domain that is a misspelling of a trusted one, with a dropped, doubled or swapped letter, a digit in place of a letter, or a different TLD, to catch users' typing errors or fool a quick reader. AdminKit's WHOIS / RDAP lookup shows who registered a suspect domain, and when.
- WHOIS — WHOIS is a simple TCP query/response protocol, defined in RFC 3912, for looking up who registered a domain name or IP address block, with no authentication and an undefined response structure. AdminKit's Whois/RDAP tool looks up a domain or IP's registration details using RDAP, the newer, structured protocol gradually replacing it.
- Wildcard DNS record — A wildcard DNS record uses an asterisk label, such as *.example.com, to answer queries for any subdomain without its own explicit record, a mechanism described in RFC 1034 and clarified in RFC 4592. AdminKit's DNS lookup tool shows exactly which record answered a query, making wildcard coverage easy to confirm.
- Zone transfer (AXFR) — A zone transfer (AXFR) is the DNS mechanism a secondary nameserver uses to copy an entire zone's records in one bulk request, meant only for legitimate replication between a domain's own servers. A server misconfigured to answer AXFR for anyone leaks every record at once. AdminKit's DNS lookup tool checks individual records the safe way.
- ZONEMD record — ZONEMD, defined in RFC 8976, is a DNS record holding a cryptographic digest of an entire zone's contents, letting a receiver verify a copy matches what the primary server published. It fills a gap DNSSEC's per-record RRSIG signatures don't cover -- AdminKit's AXFR guide explains the zone transfer a ZONEMD digest checks.
Comparisons (14)
All comparisons →- Best free DNS leak test tools (2026) | AdminKit
- Best free MX record lookup tools (2026) | AdminKit
- Best free WHOIS lookup tools (2026) | AdminKit
- AdminKit vs Dig Web Interface: DNS lookup | AdminKit
- AdminKit vs MxToolbox: a sourced comparison | AdminKit
- AdminKit vs ViewDNS.info: reverse DNS lookup | AdminKit
- AdminKit vs who.is: sourced WHOIS/RDAP comparison | AdminKit
- DNSChecker vs MxToolbox: which is better? | AdminKit
- AdminKit vs NextDNS and Control D | AdminKit
- Best Free CAA Record Generators (2026) | AdminKit
- Best Free DNS Lookup Tools (2026) | AdminKit
- Best free reverse DNS (PTR) lookup tools (2026) | AdminKit
- Best Free DNS Propagation Checkers (2026) | AdminKit
- Best Free DNSSEC Checkers (2026) | AdminKit
Related clusters
Email authentication
SPF, DKIM and DMARC are the three DNS-published records that tell receiving mail servers whether a message from your domain can be trusted — get one wrong and mail lands in spam or gets rejected outright.
IP & network
Your public IP, subnet and routing determine who can reach your connection and how it is addressed on the internet — the starting point for almost every other check on this site.
Standards & references
- RFC 1035 — Domain Names: Implementation and Specification
- RFC 8499 — DNS Terminology
- IANA — Domain Name System (DNS) Parameters registry
- IETF Datatracker — RFC 8499 canonical record
- Root Server Technical Operations Association — root-servers.org
- Microsoft Learn — DNS Zones and Records Overview (Azure DNS)
Frequently asked questions
Why doesn't a DNS change show up right away?
Every DNS record carries a TTL (time to live) in seconds, and resolvers across the internet cache the old value until that TTL expires — so a fresh record can take anywhere from minutes to the old record's full TTL to appear everywhere, even though the authoritative server already has the update. AdminKit's DNS lookup tool can query a specific resolver so you can see which ones still hold the stale answer.
What's the difference between an A record and a CNAME record?
An A record points a name directly at an IPv4 address; a CNAME record points a name at another name, which is then resolved again (RFC 1035 calls this aliasing). A domain's apex (root) generally can't use a CNAME alongside other records at the same name, which is why most DNS providers offer an ALIAS/ANAME-style workaround instead.
Why do two DNS lookup tools sometimes show different results for the same domain?
They are usually asking different resolvers, and each resolver can be at a different point in its TTL cache cycle or behind a different anycast node. AdminKit's DNS lookup tool lets you query a resolver directly so you can compare its currently cached answer against the authoritative server's.