#1 India's Top IT Training Institute

×

About Uncodemy

Know more about who we are and what we stand for.

About Us

About Us

Discover our mission to equip individuals with essential IT skills and industry expertise.

Read More →
UnCodeMy Gallery

UnCodeMy Gallery

Explore highlights from our IT training sessions and success stories.

Read More →
×

Free Resources

Learn, practice and plan your career — bilkul free.

Tutorials

Tutorials

Step-by-step written tutorials to learn any technology at your own pace.

Read More →
Free Counselling

Free Counselling

Book a free video counselling session and pick the right course for you.

Read More →
Online Compiler

Online Compiler

Write, run and test your code online — no setup required.

Read More →
🌍 FREE · STEP BY STEP

DNS Resolution Visualizer: From Name to Address

Watch how a domain name is resolved, from your browser's cache all the way to the authoritative server.

  • 🗂️ Caches at every level
  • 🪜 Root → TLD → authoritative
  • 🔀 CNAME and TTL

How to use the DNS Resolution Visualizer

  1. 1. Enter a domainAny name, such as www.uncodemy.com, and the record type.
  2. 2. Set the starting pointChoose what's already cached and which resolver you use.
  3. 3. AnimateWatch each question and answer, then copy the dig command to see the real path.

How a lookup works

When you type a web address, the browser first checks its own cache, then asks the operating system, which checks the hosts file and its cache. If nobody has the answer, the OS asks a recursive resolver (your ISP's, or a public one like 8.8.8.8 or 1.1.1.1). The resolver asks a root server, which refers it to the top-level domain servers (.com, .in…), which refer it to the domain's authoritative name servers, which give the answer. Every answer carries a TTL that says how long it may be cached. Many sites use a CNAME to a CDN, which adds another lookup. Nothing is actually looked up, so the domain you type isn't sent anywhere.

Worked example

Resolving www.uncodemy.com with nothing cached and a CNAME to a CDN takes 8 steps: browser cache miss, OS miss, the question to the resolver, the root server's referral to the .com servers (a.gtld-servers.net), the .com referral to the domain's name servers, the CNAME answer, the CDN's address (shown as the documentation address 203.0.113.10) with a 300-second TTL, and the answer back to the browser. Choose Cached at the resolver and it drops to 4 steps.

Try it for real

  • dig +trace www.example.com shows the real servers and records step by step.
  • nslookup works on Windows; resolvectl status shows your resolver on Linux.
  • Before changing DNS records, lower the TTL a day ahead so the change spreads quickly.

Frequently asked questions

Why do DNS changes take time to appear?

Resolvers keep cached answers until their TTL expires, so old records can linger for that long.

Is DNS encrypted?

Traditionally no. DNS over HTTPS (DoH) and DNS over TLS (DoT) encrypt the queries between you and the resolver.

Is the DNS visualizer free?

Yes. You can open the DNS visualizer and try everything without signing up. When you see all steps for the first time, we ask once for your name and WhatsApp number; after that it, and every other Uncodemy tool, opens straight away.

More free tools

See all free tools