Understanding DNS and IP Address Resolution
8 min read · Updated 2026
Every time you visit a website by name, a quiet translation happens in the background. DNS turns human-friendly names into the numeric addresses computers use to find each other.
It is one of the most important systems you never see. When it works, browsing feels instant; when it does not, a connection that seems perfectly healthy can suddenly fail to open pages by name.
This guide explains name resolution, the role of the DNS cache, and why DNS is a common suspect when a connection says it is working but pages will not load.
DNS server
Translates website names into numeric IP addresses your device can reach.
DNS cache
A local memory of recent lookups that speeds up repeat visits.
IP address
The numeric address that actually identifies a destination on the network.
Names versus addresses
People remember website names; computers route traffic using numeric IP addresses. DNS — the Domain Name System — is the service that bridges the two, translating a name you type into the address needed to reach it.
This translation is so fast and automatic that most people never notice it. But when it fails, the effect is very visible: a connection that appears fine yet cannot open pages by name.
How name resolution works
When you request a site by name, your device asks a DNS resolver for the matching address. The resolver may already know it, or it may ask other servers in a hierarchy until it finds the answer, which is then returned to your device so the connection can proceed.
The whole exchange usually completes in a fraction of a second, which is why browsing feels instant even though a lookup happened first.
The DNS cache
To avoid repeating lookups, your device keeps a local DNS cache — a short-term memory of recent name-to-address answers. This speeds up repeat visits because the answer is already on hand.
Occasionally a cached entry becomes stale if a site's address changes, which can cause momentary confusion until the cache refreshes. This is a normal part of how the system balances speed against accuracy.
- The cache remembers recent lookups for speed.
- Repeat visits skip a fresh lookup when cached.
- A stale entry can briefly cause confusion until refreshed.
Why DNS relates to 'no internet'
Because DNS sits above the basic connection, a DNS problem often shows up as 'connected, no internet': the link works, but names are not being resolved into addresses. Pages by name fail while the underlying connection is technically fine.
Recognising this points troubleshooting at the right layer. The issue is not the cable or the Wi-Fi signal but the name-resolution service, which is a different thing entirely.
Where DNS lives
DNS resolvers can be provided by your internet service, your router, or a third-party service you choose. Your device is usually told which one to use automatically, and it simply asks whichever resolver it has been given.
This is worth knowing because DNS is not a single place but a service that can come from different providers. It helps explain why the same site can resolve on one network and not another, even with a working connection on both.
- DNS translates website names into numeric IP addresses.
- Name resolution usually completes in a fraction of a second.
- A local cache speeds up repeat visits but can go stale.
- DNS problems often appear as 'connected, no internet'.
- Resolvers can come from your provider, router, or a chosen service.
A note on purpose
This article is educational and general in nature. Exact steps and menus vary by device, brand, and software version — always follow the official documentation for your specific hardware. Handy Guide does not offer repair, remote access, or paid support services.
Frequently asked
It is the system that translates website names into the numeric IP addresses computers use to reach each other.
The basic connection can work while name resolution fails, so pages by name will not load even though the link is up.
A short-term local memory of recent name-to-address lookups that speeds up repeat visits.
Different networks may use different DNS resolvers, so name resolution can succeed in one place and fail in another.
Related articles
NetworkingBasic Router and Wi-Fi Connection Concepts
A plain-language tour of how a router builds your home network, what the admin page is, why bands and channels matter, and how to tell a router problem from an internet problem.
NetworkingUnderstanding Wireless Network Security Settings
What Wi-Fi security types and passwords protect, why a mismatch can stop a device from connecting, and how to keep a home network private.
BrowserUnderstanding Browser Certificate Warnings
What a security certificate is, why a browser might warn you, the common reasons behind those warnings, and how to read them calmly rather than fearfully.