How to Get Started with Google Public DNS

Updated

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

Where you change it Applies to Best when
Operating system (Windows, macOS, Linux) That one device You want to test Google Public DNS without affecting others, or you only control your own machine
Router Every device on the network You want one change to cover phones, laptops, TVs, and guests
Mobile device (per Wi-Fi network) That device on that network You're on a phone/tablet and can't edit the router

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.