Software

Why a Website Resolves Differently on Different Devices

A researcher reviewing a visualisation
AI-generated illustration.
Inside this article
  1. Different resolvers, different answers
  2. Caches update on different schedules
  3. Why private names resolve only on some networks
  4. Location can affect answers
  5. Compare DNS settings on both devices

When two phones or computers open the same domain but connect to different IP addresses, they got different DNS answers. DNS looks up domain names and returns network information, such as an IP address. A DNS resolver is a server that looks up domain names for devices. Devices get different answers when they use different resolvers, have cached answers from different times, or connect through networks with different DNS rules.

Different answers are normal across resolvers, networks, or cached records. Before changing settings, connect both devices to the same network and check which DNS resolver each uses.

Different resolvers, different answers

A DNS resolver looks up a domain on a device’s behalf. Your internet provider or Wi-Fi router may supply one, while a browser or device setting may direct queries to another. Those resolvers can have different cached answers or apply different policies.

Encrypted DNS settings can send DNS lookups to a different resolver. Android’s Private DNS setting lets you select an encrypted DNS provider, while Chrome has its own secure-DNS setting. A browser’s setting can affect lookups made by that browser without changing DNS for every other app on the device. The available settings depend on the device, software version, and any management rules set by an organization.

Compare the browser’s secure-DNS setting with the operating system’s DNS settings on both devices. On Android, look under Settings → Network & internet → Private DNS. If one device uses a custom provider and the other uses the network’s default resolver, their answers may differ. Encrypted DNS protects DNS queries in transit to the selected provider; it does not encrypt all traffic or make a device’s other connections private.

Caches update on different schedules

Devices and DNS resolvers store answers temporarily to avoid repeating lookups. Each record has a time-to-live, or TTL, that tells a cache how long it can keep that answer before checking again. After a domain owner changes a record, one device may still have an older answer while another has fetched the new one. The TTL varies by record, so there is no universal waiting period for every domain.

Resolvers can also cache some failed lookups. A device that recently received an error for a domain may continue to see it briefly even after the underlying issue is resolved. If a resolver cannot reach the DNS servers that hold a domain’s official records, it can keep sending an answer after its TTL expires while it tries to get an updated one. As a result, waiting for a record’s TTL does not always explain when every device will show the same answer.

For more on why a change takes time to appear everywhere, see why DNS changes take time to propagate.

A developer working at a computer
AI-generated illustration.

Why private names resolve only on some networks

A private DNS record is a name that only resolves through a particular network, such as a company network or VPN. Organizations use this arrangement to make internal services available to authorized users while keeping those names off the public DNS.

A work laptop connected to a VPN might resolve an internal service name, while a personal phone on cellular data cannot. A custom public DNS provider can also bypass a local or VPN DNS resolver, depending on the device’s configuration. That does not prove the record is missing. For a work or school device, check the intended network or VPN connection and ask the administrator before changing DNS settings.

Location can affect answers

Some DNS services provide different addresses based on where a query appears to come from. This can help a content delivery network direct a visitor to a nearby server. The apparent location can depend on the network or resolver handling the lookup, so two devices may receive different IP addresses even when both are working as intended.

Compare the same kind of DNS record for the same domain. An A record contains an IPv4 address, while an AAAA record contains an IPv6 address. A comparison between an A answer on one device and an AAAA answer on another does not show that the devices received conflicting answers to the same query.

Compare DNS settings on both devices

Change one condition at a time to see which one affects the results. Start by putting both devices on the same Wi-Fi network and looking up the exact same domain. Then check whether either device uses a VPN, a custom Private DNS provider, or browser-specific secure DNS. If the problem appears only on one network, compare Wi-Fi with cellular data.

On Windows, nslookup example.com uses the device’s configured DNS resolver. To compare a specific resolver, use nslookup example.com followed by that resolver’s address. If you have dig, you can query the configured resolver with dig example.com A or name a resolver with dig @<DNS-server-IP> example.com A. Run the same query from both devices when possible.

On Windows, ipconfig /displaydns shows entries in the local DNS cache. After noting the result, ipconfig /flushdns clears that cache; repeat the lookup afterward. This only clears the Windows device’s local cache. It does not clear cached answers at a router, VPN, internet provider, or public DNS resolver.

For each comparison, note the domain, record type, network, resolver, and returned answer. If the answers match after you control those details, DNS is less likely to explain why the pages look or behave differently. The browser, website, or connection path may then need separate troubleshooting.

About this article

Created with AI assistance using published sources. Illustrations are AI-generated. Redbag does not claim hands-on testing or exclusive reporting. Check the linked sources for changing product details.

Our approach ↗

Keep connecting the dots.