Blog · Networking

DNS vs IP address: what’s the difference?

IP address = a locator for a machine on the internet (IPv4 or IPv6). DNS = phonebook that maps names (e.g. google.com) to those IPs.

When you open What Is My IP Address IP, we show your public IP—the one your traffic uses—not a domain’s DNS record.

What happens in one page load

When you enter a hostname, your device asks a DNS resolver (often your ISP, router, or a public resolver) for the right IP. The resolver returns A or AAAA records. Your browser then opens a TCP connection to that IP. Your own public IP is the source address those servers reply to—it is not the IP stored in DNS for example.com unless you own that domain and pointed it at yourself.

DNS records vs “my IP” tools

Tools that look up DNS show what name maps to which server. A “what is my IP” page shows the address your connection uses to reach the internet. Confusing the two is common: people paste a website’s IP into a ticket when support asked for their public IP. If you need vocabulary for both sides, read IPv4 vs IPv6 and what is a public IP address.

DNS leaks and VPNs (short version)

With a VPN, you usually want both traffic and DNS to use the VPN’s path. A “DNS leak” means queries still go to your ISP while packets use the tunnel—metadata can leak even if the site sees the VPN IP. Dedicated leak tests exist; our homepage focuses on the public IP your TCP sessions use. For VPN behavior, see what IP a VPN shows.

Practical checklist

Long-tail confusion we see often

Searchers ask whether “DNS is my IP” or whether changing DNS speeds up their connection. Changing only the resolver (e.g. to a public DNS) does not change the source address websites see for outbound connections—it changes who answers name queries. Speedups happen when the new resolver is faster or closer, not because your public IP morphed.

Another frequent mix-up: editing a domain’s DNS records at a registrar versus reading “my IP” for your home line. Registrar DNS controls where yourdomain.com points; it has nothing to do with the DHCP address your ISP assigns unless you deliberately point a record at your home IP for hosting.

People also ask

What is a DNS server “address”? Resolvers have IPs too (e.g. 8.8.8.8)—that is where you send queries, not “your” client IP story.

Does DNS affect gaming ping? Only indirectly—if name resolution is slow or wrong region, picking a faster resolver can help; it does not replace good routing.

Can DNS filtering block malware? Some providers block known bad domains—that is separate from hiding your IP.

Extended guide: study notes for beginners

Write two columns on paper: “DNS maps names to IPs” vs “My public IP is my source address on the internet.” Drill until the distinction is automatic—confusion here wastes hours in misfiled tickets.

When a site is “down,” check DNS resolution separately from ping/traceroute—sometimes the name fails while the IP still answers if you knew it.

HTTPS protects content on the wire; DNS over HTTPS/TLS protects query privacy from local observers—different layers, both useful.

Advanced readers can explore split-horizon DNS where internal names resolve differently than public—home labs sometimes do this for services.

Common mix-ups in real tickets

Users say “I changed my DNS to 1.1.1.1 but my IP did not change.” Correct—DNS settings alter resolver choice, not your source address. Fix the misunderstanding before chasing ISP outages.

Another pattern: “The site resolves but won’t load.” That can be TCP/HTTPS issues, geo blocks, or path MTU—not DNS at all. Isolate by trying the IP directly only when safe and appropriate; many hosts serve multiple sites per IP via SNI.

Ad blockers and hosts files override DNS locally. A corporate laptop might resolve internal names while your phone on LTE resolves public ones—behavior diverges even though both “use the internet.”

Reverse DNS maps IP to name sometimes; consumers rarely control PTR records—mention that when hobbyists expect custom reverse lookups on residential lines.

Summary checklist

DNS answers “where is this name?” Your IP checker answers “what address am I using?” Keep questions separate during debugging.

Related guides