Verizon Fios DNS Settings: How to Change, Fix, and Optimize

Verizon Fios delivers some of the fastest fiber internet in the United States, but its default DNS servers are not always the most reliable or the quickest. If you are experiencing slow page loads, intermittent DNS resolution failures, or sites that simply refuse to open despite a working connection, the root cause is often Fios's own DNS infrastructure. The good news is that changing your DNS settings on a Fios gateway is straightforward once you know exactly where to look, and the performance and reliability gains can be immediate and significant.

Why Verizon Fios DNS Can Cause Problems

Verizon Fios customers are automatically assigned Verizon's recursive DNS resolvers, typically 4.2.2.1 and 4.2.2.2 (sometimes appearing as 71.242.x.x or 71.243.x.x ranges depending on your region). These servers handle billions of queries daily and occasionally suffer from:

• High latency: Verizon's DNS nodes may not be geographically close to your actual location, adding unnecessary round-trip time to every domain lookup.
• Slow propagation updates: Cached records can be stale, meaning a site that recently changed its IP address may not resolve correctly for longer than it should.
• Intermittent outages: Like any public infrastructure, Verizon DNS servers go down or become degraded, causing sporadic failures that look like internet outages but are actually DNS-only issues.
• NXDOMAIN hijacking: Verizon historically redirected failed DNS lookups to a search page rather than returning a proper NXDOMAIN error, which can break applications and scripts that rely on proper error responses.

Switching to a faster, more reliable third-party DNS resolver like Cloudflare (1.1.1.1), Google (8.8.8.8), or Quad9 (9.9.9.9) solves most of these issues without touching any other part of your network configuration.

Identify Your Fios Gateway Model

Verizon Fios deploys several different gateway models. Knowing which one you have determines exactly which admin interface you will encounter:

• Fios Home Router (G3100): The newer Wi-Fi 6 gateway, typically administered at 192.168.1.1 or myfiosgateway.com.
• Fios Quantum Gateway (G1100): The most widely deployed model, also at 192.168.1.1 or myfiosgateway.com.
• Actiontec MI424WR: An older model still found in some Fios installations, administered at 192.168.1.1.
• Fios Router (CR1000A/CR1000B): The latest generation multi-gig router, accessed via 192.168.1.1 or myfiosgateway.com.

In almost all cases, typing http://192.168.1.1 into a browser on a device connected to your Fios network will reach the admin panel. The default username is admin and the default password is printed on the sticker on the side or bottom of the gateway. If you changed it at setup, use your custom credentials.

Choosing the Right DNS Servers

Before diving into the router settings, decide which DNS servers you want to use. Here are the most reliable public options:

• Cloudflare DNS: Primary 1.1.1.1 / Secondary 1.0.0.1 — consistently the fastest globally, strong privacy policy, no query logging sold to third parties.
• Google Public DNS: Primary 8.8.8.8 / Secondary 8.8.4.4 — rock-solid reliability and very low latency in most US regions.
• Quad9: Primary 9.9.9.9 / Secondary 149.112.112.112 — blocks known malicious domains by default, good choice for families or small offices.
• OpenDNS (Cisco): Primary 208.67.222.222 / Secondary 208.67.220.220 — excellent uptime, optional content filtering via the OpenDNS dashboard.

How to Change DNS on the Fios Quantum Gateway G1100 and G3100

These two models share a very similar admin interface. Follow these exact steps:

1. Open a browser and navigate to http://192.168.1.1 or http://myfiosgateway.com.
2. Log in with your admin credentials.
3. Click My Network in the top navigation bar.
4. Select Network Connections from the left-hand menu.
5. Click on Broadband Connection (Ethernet/Coax) — this is the WAN interface.
6. Click Settings (or the gear/edit icon next to the connection).
7. Scroll down to the DNS Server section. You will see fields for Primary DNS and Secondary DNS currently populated with Verizon's addresses.
8. Clear both fields and enter your preferred DNS servers. For Cloudflare: Primary 1.1.1.1, Secondary 1.0.0.1.
9. Click Apply and wait 10-15 seconds for the gateway to save the settings.
10. Restart your browser and test a few sites.

If you want all devices on your network to use the new DNS automatically (without configuring each device individually), also update the DNS settings under the DHCP Settings section. In the same Network Connections area, click on your local network (usually labeled Network (Home/Office)), then navigate to the IP Address Distribution or DHCP tab. Enter your new DNS servers in the DNS fields there. This pushes the new resolvers to all devices that obtain their IP via DHCP when they renew their lease.

How to Change DNS on the Actiontec MI424WR

1. Navigate to http://192.168.1.1 and log in.
2. Click the My Network icon at the top.
3. Select Network Connections, then click Broadband Connection (Coax) or Broadband Connection (Ethernet) depending on your setup.
4. Click Settings.
5. Under Internet Protocol, find the DNS fields. Change them to your preferred servers.
6. Click Apply.

Changing DNS on Individual Devices Without Touching the Router

If you do not want to change the router-level DNS (for example, if Verizon manages the gateway and you do not have full admin access), you can set DNS per device. This overrides whatever the router pushes via DHCP.

Windows 10 and 11

1. Open Settings and go to Network and Internet.
2. Click Change adapter options (on Windows 10) or click your active connection and then Hardware properties (on Windows 11).
3. Right-click your active adapter (Ethernet or Wi-Fi) and select Properties.
4. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
5. Choose Use the following DNS server addresses and enter your preferred servers.
6. Click OK and close all windows.

Repeat the same steps for Internet Protocol Version 6 (TCP/IPv6) if you use IPv6, entering Cloudflare's IPv6 addresses: 2606:4700:4700::1111 (primary) and 2606:4700:4700::1001 (secondary).

macOS

1. Open System Settings (or System Preferences on older macOS) and go to Network.
2. Select your active connection (Wi-Fi or Ethernet) and click Details (or Advanced).
3. Go to the DNS tab.
4. Click the + button and add your preferred DNS server addresses.
5. Click OK then Apply.

Android and iOS

On Android, go to Settings > Network and Internet > Wi-Fi, long-press your connected network, select Modify network, change IP settings to Static, and enter the DNS addresses. On iOS, go to Settings > Wi-Fi, tap the info icon next to your network, scroll to Configure DNS, switch to Manual, and add your DNS server entries.

Alternatively, install the 1.1.1.1 app from Cloudflare on mobile, which creates a local VPN profile that routes all DNS queries through Cloudflare's servers without needing static IP configuration.

Verifying Your New DNS Settings Work Correctly

After making changes, do not just assume everything worked. Run these quick checks:

On Windows using Command Prompt

The output of ipconfig /all will show the DNS Servers currently configured for each adapter. The nslookup commands confirm that queries are resolving and that your chosen server is responding correctly. If the second nslookup returns a result and the first does not, your DHCP-assigned DNS is still broken and the router change may not have taken effect yet.

On macOS and Linux using Terminal

The dig command shows exactly which server answered the query and how long it took (the Query time line). Compare the query time with and without the @1.1.1.1 argument. A well-configured Cloudflare or Google resolver should return results in under 20ms for most US locations.

You can also use the DNS Lookup tool to query any domain name and see exactly which IP addresses are being returned by public resolvers right now. This is especially useful if you suspect a specific domain is resolving incorrectly.

Fixing Common Fios DNS Errors

DNS_PROBE_FINISHED_NXDOMAIN in Chrome

This error almost always means the DNS query returned no result. After changing your DNS servers, flush the DNS cache on both your device and browser. In Chrome, navigate to chrome://net-internals/#dns and click Clear host cache. Also run ipconfig /flushdns on Windows or sudo dscacheutil -flushcache on macOS.

Slow DNS Resolution Despite New Servers

If you set a custom DNS on the router but clients still seem slow, check whether the router itself is set as the DNS server in DHCP (meaning it appears as 192.168.1.1 in your client's DNS config, and then forwards to your chosen upstream). Some Fios gateways use a local DNS relay/proxy. To bypass this, set the DNS directly on your device rather than relying on the gateway's DHCP settings, or confirm in the router's DHCP settings that it is handing out your chosen DNS IP directly rather than its own LAN IP.

Certain Sites Not Loading After DNS Change

This is usually a stale cache issue. Flush the DNS cache on the device and restart the browser. If a specific site still fails, test it with a manual nslookup against multiple resolvers to determine whether the problem is DNS-specific or a connectivity issue with that origin server.

DHCP Lease Not Picking Up New DNS

Devices hold onto their DHCP-assigned DNS until the lease renews, which can be hours. Force an immediate renewal:

How to Benchmark DNS Performance on Fios

Before committing to a specific DNS provider, benchmark your actual response times from your Fios connection. Download and run DNS Benchmark (Gibson Research Corporation, free, Windows) or use namebench (cross-platform, open source). These tools query dozens of public resolvers and rank them by speed from your specific location on your specific connection. What works fastest on a Comcast line in Chicago may differ from Fios in New Jersey.

Typical Fios results show Cloudflare 1.1.1.1 and Google 8.8.8.8 performing nearly identically, both well under 15ms average. Verizon's own resolvers typically land between 20-45ms in the same tests, which compounds across every page load since modern websites involve dozens of DNS lookups per page.

Preventing DNS Problems on Fios Going Forward

• Document your settings: Note the DNS servers you chose and where you configured them (router, specific devices, or both). This saves time if you ever need to factory reset the gateway after a firmware update.
• Enable DNS over HTTPS (DoH) or DNS over TLS (DoT): Both Cloudflare and Google support encrypted DNS. On Windows 11, you can enable DoH natively in the network adapter settings. This prevents your ISP from seeing your DNS queries in plaintext.
• Check your DNS settings after firmware updates: Verizon occasionally pushes automatic firmware updates to Fios gateways that can reset certain configurations. Verify your DNS settings a few days after any gateway reboot.
• Set both a primary and secondary resolver: Never leave the secondary field blank. If the primary is unreachable, the OS falls back to the secondary. Use servers from different networks for maximum resilience (for example, Cloudflare primary and Google secondary).
• Monitor with periodic checks: Bookmark the DNS Propagation Checker and run a quick check if you ever suspect DNS issues are back. Catching a partial outage at the resolver level early prevents hours of unnecessary troubleshooting.

A Note on IPv6 and Fios

Verizon Fios has supported native IPv6 for many years, and your gateway likely has IPv6 enabled by default. If you switch your IPv4 DNS but leave IPv6 DNS untouched, devices that prefer IPv6 may still use Verizon's IPv6 DNS resolvers. On the G1100 and G3100, IPv6 DNS settings are in the same Broadband Connection settings panel under the IPv6 section. Cloudflare's IPv6 DNS addresses are 2606:4700:4700::1111 and 2606:4700:4700::1001. Google's are 2001:4860:4860::8888 and 2001:4860:4860::8844. Set both to ensure full coverage regardless of which protocol your device uses for a given connection.