IPv4 and IPv6 Preference Producing Different Results

IPv4 and IPv6 Preference Producing Different Results

TL;DR / Summary: When an IP lookup shows one address on one device and a different one on another, the cause is usually IPv4 versus IPv6 preference, not a network fault. Check both protocol families before assuming something is wrong.

Two addresses, one connection

A modern network connection has both an IPv4 address and an IPv6 address. Which one a site or service sees depends on the preference of the client, the resolver, and the destination’s configuration.

An IP lookup that queries only one family will report one address, and a second lookup that queries the other will report another. Both are correct.

That is the most common explanation for a “different IP” surprise, and it is benign in most cases.

How the preference is decided

Operating systems generally prefer IPv6 when it is available and working. If the IPv6 path fails, the client falls back to IPv4, sometimes after a delay that users notice as a slow page load.

Browsers implement a happy-eyeballs approach, attempting both families and using whichever connects first. That means the family used can vary between requests, and therefore the address reported can vary.

  • IPv6 preferred — the default on most modern systems
  • IPv4 fallback — used when IPv6 fails or is slower
  • Application-level preference — some tools force one family
  • Resolver choice — determines which record is returned first

Why a lookup tool reports one family

Many lookup services accept a connection and report the source address of that connection. If the service is IPv4-only, it will always see the IPv4 address, even if your network prefers IPv6.

A service that supports both will see whichever your client chose. Comparing two such services can produce two different addresses for the same device.

Checking both families

Look for a lookup that explicitly shows both IPv4 and IPv6 results. If it shows only one, the other is unknown rather than absent.

On the device, check the network settings to see whether an IPv6 address is assigned. A network without IPv6 will only ever produce IPv4 results.

Use a command-line check on the device itself for a definitive answer, rather than relying on a web page that may be constrained by its own connectivity.

Two addresses is normal. No address is a problem.

When the difference is not IPv6

Other explanations exist and should be ruled out in order of likelihood.

A VPN or proxy changes the egress address, and different applications may route differently. Split tunnelling means some traffic uses the tunnel and some does not.

Carrier-grade NAT means the address you see is shared with many subscribers and can change without warning. Mobile networks change addresses frequently, sometimes mid-session.

Corporate networks often have multiple egress points, and a device may leave through a different one depending on which internal route it takes.

What actually matters

For most purposes, the address itself is not important. What matters is whether the service you are using accepts the connection and whether geolocation or access rules behave as expected.

If a site blocks you based on location, the relevant question is which address that site sees, not which address a generic lookup shows. Test the specific service.

If you need a stable address for allowlisting, an IPv6 address may be more stable than a shared IPv4, or the reverse, depending on the network.

Documenting the difference

When troubleshooting support tickets, record both addresses and which family each belongs to. A ticket that says “my IP is X” without a family is ambiguous.

Note the time of the check as well. Mobile addresses rotate, and a screenshot from yesterday may not describe today.

Keep a short note of which lookup tools report which family. It saves repeating the same confusion on the next ticket.

A quick diagnostic order

First, confirm both families on the device. Second, check whether the lookup service supports both. Third, test the specific service that is misbehaving.

Only then investigate VPNs, proxies, and carrier NAT. Starting with the exotic explanations wastes time on a problem that is usually a protocol preference.

For a lookup that separates the families clearly, my IP inquire is a reasonable reference, particularly when comparing results across devices.

IPv4 and IPv6 are supposed to coexist. Treating the difference as a fault is the real error, and checking the family first resolves most of these questions in a minute.

What a dual-stack lookup looks like

A lookup that supports both families usually presents two results, or a single result with a toggle. The toggle is the useful part, because it lets you see both addresses for the same connection.

If only one family is shown, check whether the service itself is reachable over the other. An IPv4-only service cannot report an IPv6 address no matter what the client prefers.

Some services also report the protocol used for the connection, which removes the ambiguity entirely. That field is worth looking for before drawing conclusions from the address alone.

Testing preference deliberately

On a desktop system, it is often possible to disable one family temporarily and observe the fallback. That is a diagnostic tool, not a permanent setting, and it should be reverted.

Disabling IPv6 temporarily and seeing whether everything still works tells you how dependent you are on it. On most home networks the answer is “not much,” which is reassuring rather than alarming.

Re-enable it afterward. A permanently disabled IPv6 stack is a common shortcut that becomes a long-term limitation, especially on networks that are IPv6-first.

Similar Posts