dns.google

Go to dns.google, type a domain (like example.com) or an IP address (like 8.8.8.8 or 2001:4860:4860::8844) into the DNS Name field, and select Resolve. The page returns the DNS records associated with that name or address. This works for both IPv4 and IPv6 formats, and it's useful when you want to confirm how a name resolves or check what a given address maps back to.

Steps to run a lookup

1. Open https://dns.google in your browser.
2. Find the DNS Name input field.
3. Enter one of the following:
   • A domain name, e.g. example.com
   • An IPv4 address, e.g. 8.8.8.8
   • An IPv6 address, e.g. 2001:4860:4860::8844
4. Click Resolve.
5. Read the returned DNS resolution results in the response area.

The input accepts either a name or an address, so you don't need to switch tools depending on what you're checking.

What you can enter

Both address families are supported, which matters if you're troubleshooting a site that behaves differently over IPv4 and IPv6.

What the results tell you

After you select Resolve, the page shows the DNS resolution output for your input. You can use this to:

• Confirm whether a domain resolves at all.
• Check which records a name returns.
• Verify that an IP address is associated with the expected name.

If a domain you expect to resolve returns nothing or unexpected records, that points to a DNS configuration or propagation issue rather than a problem with the lookup tool itself.

Related options on the page

Alongside the lookup field, the page links to Help, Cache Flush, and Get Started with Google Public DNS. Cache Flush is relevant if you've recently changed DNS records and want to clear cached entries before re-checking; the Get Started page covers using Google Public DNS as your resolver rather than just querying through the web tool.

Common snags

• Typo in the name or address: A single wrong character changes the query entirely. Re-check the exact spelling before concluding a record is missing.
• Expecting a full record dump: The tool returns resolution results for what you entered; it isn't a general-purpose zone viewer.
• Confusing lookup with changing your resolver: Querying on dns.google shows you results, but it doesn't change which DNS server your own device uses. For that, follow the Get Started guidance.

Cache Flush on Google Public DNS asks Google's resolvers to discard cached DNS records for a domain you specify, so the next lookup is fetched fresh from authoritative name servers. It is useful when a domain's records have changed but Google Public DNS still returns the old answer. It does not change your domain's DNS configuration, and it does not clear the cache on your own device, router, or ISP resolver.

What Cache Flush actually does

Google Public DNS caches answers to reduce lookup time and load on authoritative servers. Each cached record has a TTL (time to live) set by the domain's owner. Until that TTL expires, Google's resolvers can keep serving the cached copy.

Cache Flush submits a request to Google Public DNS to remove cached records for a specific domain name. After that, the next query for the domain is resolved again from the authoritative name servers, so a recent record change can appear sooner than waiting for the TTL to run out.

The dns.google page lists Cache Flush alongside Resolve and Help, and the Resolve tool accepts a domain like example.com or an IP address like 8.8.8.8 or 2001:4860:4860::8844. Cache Flush is the part of that toolkit aimed at refreshing cached records rather than looking them up.

When to use it

Use Cache Flush when all of these are true:

• You changed DNS records for a domain (for example, a new A, AAAA, or CNAME target).
• You are checking the result through Google Public DNS (8.8.8.8, 8.8.4.4, or 2001:4860:4860::8888 / ::8844).
• Google Public DNS still returns the old value while the authoritative servers already return the new one.

A typical sequence:

1. Update the record at your DNS provider.
2. Confirm the authoritative name servers return the new value.
3. Query the domain through Google Public DNS and see whether it still returns the old value.
4. If it does, submit a Cache Flush for that domain.
5. Query again and check whether the new value appears.

If the authoritative servers still return the old value, Cache Flush will not help — the problem is upstream of Google's cache.

Cache Flush vs. waiting for TTL

These are separate caches. Flushing Google's cache does not flush your operating system's cache, your browser's cache, or your router's cache, and vice versa. If a stale answer comes from your own device, Cache Flush on dns.google will not fix it.

What Cache Flush does not do

• It does not modify the domain's DNS records. Records are controlled at your DNS provider or authoritative name servers.
• It does not change TTL values. TTLs are set by the domain owner.
• It does not guarantee an instant global update. Other resolvers, and other Google Public DNS locations, may still hold cached copies until their TTLs expire.
• It does not clear caches on your device, browser, router, or ISP.

Common snags

• The record still looks old after flushing. Check the authoritative name servers directly. If they return the old value, the change has not propagated to them yet.
• Only some queries show the new value. Different resolvers and different Google Public DNS nodes can be at different cache states; results may vary until TTLs expire everywhere.
• You flushed but your browser still shows the old site. That is a local or browser cache issue, not a Google Public DNS cache issue.
• You are not using Google Public DNS. Cache Flush only affects Google's resolvers. If your device is configured to use another resolver, flushing Google's cache will not change what you see.

Quick check

Before flushing, verify where the stale answer is coming from. Query the domain through Google Public DNS and compare it with a direct query to the authoritative name servers. If Google is stale and the authoritative servers are current, Cache Flush is the right tool. If both are stale, wait for the change to reach the authoritative servers first.

To get started with Google Public DNS, change the DNS server addresses on your device or router to Google's public resolvers, then verify the change with a lookup on dns.google. Google Public DNS is a free public resolver service; you don't install an app, you point your existing network settings at Google's addresses. The main decision is where to make the change: a single device (per-device control, easy to undo) or your router (applies to every device on the network at once).

What you need before you start

• The Google Public DNS addresses:
  • IPv4: 8.8.8.8 and 8.8.4.4
  • IPv6: 2001:4860:4860::8888 and 2001:4860:4860::8844
• Access to your device's network settings, or your router's admin interface if you want a network-wide change.
• A way to test afterward — the lookup tool on dns.google, or a command-line query.

Step 1: Choose where to configure it

If you're unsure, start with your operating system. It's the easiest to reverse if something behaves unexpectedly.

Step 2: Change the DNS servers

The exact menu path differs by platform, but the action is the same everywhere: find the network adapter or Wi-Fi connection you're using, open its properties, and replace the existing DNS server entries with the Google addresses above.

• Windows: Network adapter properties → Internet Protocol Version 4 (TCP/IPv4) → "Use the following DNS server addresses."
• macOS: System network settings → your active connection → DNS → add the Google addresses.
• Router: Look for a "DNS" or "Internet/WAN" section in the admin panel and enter the addresses there. Router interfaces vary widely, so consult your router's own documentation for the exact field.
• Mobile: In the Wi-Fi settings for the connected network, switch from automatic to manual DNS and enter the addresses.

Enter both the primary and secondary address so there's a fallback if one is unreachable.

Step 3: Verify it's working

After saving, confirm the change took effect rather than assuming it did.

1. Open dns.google in a browser.
2. Enter a domain (like example.com) or an IP address (like 8.8.8.8 or 2001:4860:4860::8844) into the DNS Name field.
3. Resolve it and check that you get a sensible answer back.

The dns.google page also exposes Resolve, Help, Cache Flush, and Get Started options — the Get Started entry is the official configuration guidance if you want Google's own instructions for your platform.

You can also test from a terminal: query a domain and confirm the response comes back correctly. If lookups still fail or return unexpected results, the setting likely didn't save or another DNS source (like a VPN) is overriding it.

Common snags

• VPN or security software overrides your DNS. Many VPNs force their own resolvers, so your manual setting is ignored while connected.
• You edited the wrong adapter. Laptops often have both Wi-Fi and Ethernet entries; change the one actually carrying traffic.
• Router change didn't propagate. Some devices cache DNS or need a reconnect (toggle Wi-Fi off/on) to pick up the new resolver.
• Only one address entered. Add both primary and secondary to avoid a single point of failure.

When this is worth doing

Switching to Google Public DNS makes sense if you want a well-known public resolver and a straightforward way to verify results through dns.google. If your goal is a network-wide change with minimal per-device work, configure the router; if you just want to try it safely, configure one device first and confirm with a lookup before rolling it out further.

dns.google is the web interface for Google Public DNS, a public DNS resolution service. You can use it to look up how a domain name resolves (for example, example.com) or to check what a given IP address (such as 8.8.8.8 or 2001:4860:4860::8844) resolves to. It is aimed at ordinary users and developers who need public DNS resolution and a quick way to inspect DNS answers from a browser.

What dns.google Does

The service resolves DNS queries on Google's public infrastructure. Instead of installing a tool or changing your device settings, you can enter a domain or IP address on the page and get the resolution result directly.

The page exposes three main entry points:

• Resolve — run a DNS lookup for a domain name or IP address.
• Cache Flush — clear cached DNS entries.
• Get Started with Google Public DNS — guidance for adopting Google Public DNS.

How to Use It

1. Open dns.google.
2. In the DNS Name field, enter a domain (like example.com) or an IP address (like 8.8.8.8 or 2001:4860:4860::8844).
3. Submit the query and read the resolution result.

The expected outcome is the DNS answer for the name or address you entered, which helps you confirm how a record currently resolves.

When It Is Useful

• Checking whether a domain resolves as expected.
• Inspecting resolution for a specific IP address.
• Flushing cached entries when stale DNS data may be causing problems.
• Getting started with Google Public DNS as your resolver.

Key Details

If you only need to resolve a name or check an address, the Resolve function is the direct path. If you are setting up Google Public DNS for the first time, start with the Get Started entry.