DNS Lookup — Every Record Type, Live

About the DNS Lookup

Behind every domain name sits a phone book. When you type digitalkasur.com into a browser, something has to turn that name into the machine address your device actually connects to — that something is DNS, the domain name system, and its individual entries are called records. Site owners meet DNS at every important moment: pointing a domain at new hosting, receiving email through Google Workspace or Zoho, proving domain ownership to Meta or Google Search Console.

This tool reads those records directly from Google's public DNS resolver — the same 8.8.8.8 service answering billions of queries a day. Pick a domain, pick a record type, and the raw answers come back with their TTLs (time to live, the seconds other servers may cache them): A records show the IPv4 addresses a domain resolves to, MX records list the mail servers responsible for its email in priority order, NS records name the authoritative nameservers, TXT records carry ownership proofs and anti-spam policies, and CNAME and SOA round out the aliases and zone administration.

For most everyday problems, two lookups are enough. Site not loading after a hosting move? Check the A record — if it still shows the old server IP, the change has not propagated (send it to the propagation checker next). Email not arriving? Check MX — a missing or wrong-priority MX is the cause more often than the mailbox itself. The tool runs entirely in your browser against the public API; nothing is logged here because there is no here to log anything on.

How to Use the DNS Lookup

Follow these simple steps — the whole process takes under a minute:

1. Type the domain — just the name, like example.com; https:// and paths are stripped automatically.
2. Pick the record type — A for website IPs, MX for mail, TXT for verification strings, NS for nameservers, CNAME for aliases, AAAA for IPv6, SOA for zone details.
3. Press Lookup — answers arrive in about a second, straight from Google's public resolver.
4. Read each row — the left column is the record name, the right shows its value and TTL in seconds (300 means five minutes of caching).
5. Compare after changes — rerun the lookup after editing records at your registrar; new answers plus falling TTLs mean the change is going live.

The Formula & Method Behind the DNS Lookup

A DNS query has two inputs and one answer set. The query for digitalkasur.com type A returns, in a real session, the addresses 104.21.94.242 and 172.67.135.25 with a TTL of 300 — meaning the domain's site lives behind two cloud addresses, and any resolver worldwide may keep that answer for five minutes before asking again. The tool displays exactly this: name, value, TTL, repeated for every answer record the zone holds.

Each record type answers a different practical question. A and AAAA map a name to IPv4 or IPv6 addresses — the website's home. MX carries a priority number before each hostname; mail goes to the lowest number first, so "5 alt1" style rows are fallbacks, not duplicates. CNAME is an alias pointing one name at another — www often CNAMEs to the apex. NS names the servers with the final say over the zone. TXT holds arbitrary text: SPF policies that decide who may send the domain's email, DKIM signing keys, and the site-verification strings Google and Meta ask for.

Failure modes have meaning too. Status 3 is NXDOMAIN — the domain does not exist, usually a typo or an expired registration. A successful query with no answers means the domain exists but holds no records of that type — normal for TXT on a small site, a red flag for MX on one that should receive mail. And an A record pointing at 127.0.0.1 or 0.0.0.0 is usually a parked or deliberately blackholed entry. Reading these three cases turns "the site is broken" into a specific sentence you can act on.

DNS in Practice — Migrations, Mail and Verification

Moving hosting without downtime. The safe sequence is: lower the A record's TTL to 300 a day before the move, switch hosting, update the A record, then watch this lookup until the new IP appears. Because resolvers cache by TTL, a low TTL turns an hour of stale answers into five minutes. Raise the TTL again once the new address is confirmed everywhere — long TTLs are good for stability once things are settled.

Email lives and dies on MX and TXT. Mail that bounces for one recipient but not another usually means one of three rows is wrong: the MX hostnames, the SPF TXT that authorises your sender, or the DKIM TXT that signs it. Read them here exactly as the outside world sees them — a record you have not verified publicly is a record that does not exist. The DNS propagation checker shows whether different resolvers agree yet.

Verification strings are TXT records. Google Search Console, Meta Business and most SSL authorities ask you to paste a string into DNS, then check it from outside. Paste it, wait for the TTL, and look it up here before pressing their verify button — it saves a failed attempt and a 24-hour lockout.

Records resolve to addresses, and addresses have owners. Once your A record shows an IP, the IP address lookup reveals which network and country that server sits in — useful for sanity-checking a hosting purchase or decoding a suspicious MX host. Together the two tools cover a domain's full public footprint.