Services AI Systems & Intelligent Automation Cloud Platforms & Enterprise Architecture Cybersecurity, Identity & Governance Systems Integration & Business Automation Intelligent Web Platforms Infrastructure & Networking Managed Technology Services Case Study Industries Free tools About Contact Talk to an Architect
  1. Home
  2. Free tools
  3. DNS lookup
Tool 04 · DNS

Look up any record. See whether it has propagated.

Query A, AAAA, MX, NS, TXT, CNAME, SOA, CAA and SRV records through public resolvers, reverse-resolve an IP address, or ask every authoritative name server for the zone directly to confirm a change has taken effect.

Results are indicative and based on public DNS and HTTP responses at the moment you run the check. They are not a security audit or a compliance finding. See the terms.

Reading the result

Record types, and what propagation actually is.

Record types

  • A / AAAA: the IPv4 and IPv6 addresses a name points to. Each address links to a reverse lookup.
  • MX: the servers that receive mail for the domain, in priority order (lower first).
  • NS: the name servers that hold the zone. If these are wrong, nothing else matters.
  • TXT: free text, used for SPF, DMARC, DKIM, domain verification (Google, Microsoft, Apple) and more.
  • CNAME: an alias to another name. A name with a CNAME cannot have other records.
  • SOA: the zone's start of authority: primary server, contact, serial number and timers. The serial changes on every edit, which makes it a quick way to see whether a change has landed.
  • CAA: which certificate authorities may issue certificates for the domain.
  • SRV: service locations, used by Microsoft 365 for Teams federation and by other services, in the form _service._proto.domain.
  • PTR: reverse lookup, mapping an IP address back to a name. Mail servers without a matching PTR are often rejected.

Propagation

DNS does not push changes anywhere. When you edit a record, only your authoritative name servers know about it; every other resolver on the internet keeps serving its cached copy until that copy's TTL runs out. "Propagation" is just caches expiring, which is why a change can be visible from one network and not another.

Tick the propagation box and the tool finds the zone's NS records, then queries each of those servers directly and compares their answers. If the authoritative servers agree with each other but public resolvers still show the old value, you are waiting on TTL. If the authoritative servers disagree with each other, the change has not replicated between them, or the domain's NS records point at a server that no longer hosts the zone, which is a common leftover after moving providers.

Common questions

Which resolvers does the tool use?
Cloudflare (1.1.1.1) and Google (8.8.8.8) public DNS, with a fallback to the server's own resolver if those time out. Answers can be cached for up to the record's TTL, so a change you made a minute ago may not appear until you use the propagation check.
I changed my MX records and the old ones still show.
Check the propagation box. If the authoritative servers already return the new records, the change is done and the rest is caching. If they still return the old ones, the edit did not save, or it was made at a different DNS provider than the one your NS records point to.
Why is there no PTR for my server?
Reverse DNS is controlled by whoever owns the IP address, which is usually your hosting provider or ISP, not your domain registrar. Ask them to set it. For outbound mail servers this matters.
Next step

Migrating a domain, a tenant or a website?

DNS is where migrations go wrong at 5pm on a Friday. We plan the record changes, lower the TTLs in advance, and cut over with a rollback path.