A browser can display a friendly name such as nikh.im, but routers forward traffic using network addresses. DNS bridges those worlds by translating a hostname into address information a client can use.
What Is an IP Address?
What an IP Address Represents
An IP address identifies a network interface participating in an IP network. IPv4 addresses look like 93.184.216.34, while IPv6 addresses look like 2001:4860:4860::8888. Think of an address as a network destination, not a permanent identity for one physical server.
Large sites can return several addresses, direct users toward nearby infrastructure, place a CDN in front of an origin, or change an address without changing the domain. Many hostnames can also point to the same frontend.
Why Domain Names Exist
Names such as github.com are easier to remember and can stay stable while infrastructure changes. DNS is a distributed naming system, not one global server that receives every lookup.
How Domains and DNS Work
Browser cache -> Operating system cache -> Recursive resolver -> DNS hierarchy -> Authoritative server -> Cached answer
A Typical DNS Resolution
The browser and operating system first check cached information. If neither has a usable answer, a recursive resolver—often operated by an ISP, company, or public DNS provider—does the lookup. If needed, it follows DNS delegations until it reaches authoritative information for the domain.
The result may contain an A record for IPv4, an AAAA record for IPv6, or a CNAME alias that leads to another name. Records include a time to live so clients and resolvers can reuse answers for a limited period.
Conceptual DNS exchange
Question: Which address belongs to example.com?Answer: example.com -> 93.184.216.34TTL: cache this answer for a limited periodDNS Does Not Fetch the Website
DNS only helps locate a network destination. The client still chooses a route, contacts a port, establishes transport and security, then sends HTTP. A successful lookup does not prove that the application is healthy.
Caching Explains Propagation Delays
Caching improves speed and reduces DNS load, but a record change is not visible everywhere at once. During a migration, two users may temporarily receive different valid answers because their resolvers cached records at different times.
- Use dig or nslookup to inspect resolver answers.
- Check both A and AAAA records when IPv4 and IPv6 behavior differs.
- Remember that a hosts file or enterprise DNS can override public answers.
- Treat NXDOMAIN, resolver timeout, and connection failure after a correct answer as different problems.
The boundary
DNS answers where a name points. IP routing determines how packets travel there; neither guarantees that the destination service will respond.
Series
How Internet Requests Actually WorkAn eight-part beginner series tracing internet communication from an HTTP request through DNS, IP, ports, transport protocols, packets, network devices, server infrastructure, security, and troubleshooting.
HTTP Requests: Methods, URLs, Headers, and Bodies
Start at the application layer and understand what a browser or API client is actually asking for.
DNS, Domain Names, and IP Addresses
Follow the lookup that turns a human-friendly hostname into a network destination.
Public IP, Private IP, NAT, and Ports
See how local devices reach the internet and how operating systems identify each service and flow.
TCP vs UDP
Compare reliable byte streams with simpler datagrams and understand where each transport fits.
Packets, Network Layers, Switches, and Routers
Learn how data is encapsulated and moved across local links and routed networks.
The Complete Website Request Journey
Put the layers together from the browser to production infrastructure and back again.
HTTPS, TLS, and HTTP Status Codes
Understand secure transport, certificate checks, and the response codes used during debugging.
Troubleshooting, Localhost, Cloud, and Containers
Apply the model with diagnostic tools and carry it into cloud and container environments.
Nikhlesh Yadav is a Technical Lead and Solution Architect with 12+ years of experience across cloud-native systems, distributed platforms, AI integrations, Web3, and cyber security.
Read full profile