eero uses your internet service provider's (ISP) DNS servers by default, but you can configure custom DNS servers for additional reliability or advanced features.
How do I set up custom DNS servers with eero?
You can use the eero App to set custom DNS servers for IPv4 and IPv6. Use the following instructions to change your DNS settings:
- Open the eero App, and tap Settings in the bottom-right corner
- Tap Advanced networking
- Tap DNS
- On the DNS page, tap the button next to Custom DNS
- Input your desired IPv4 and/or IPv6 nameserver addresses
- Tap Save in the top-right corner
This will reboot your network to propagate the settings across your devices.
Why are my DNS settings grayed out?
If you are an eero Plus user, this is expected when eero Plus is enabled. eero Plus works by filtering DNS requests from devices, so custom DNS settings won't work as expected.
Your devices may still show that they are using either your ISP DNS servers or any custom DNS servers you set previously via DHCP. However, eero Plus works by filtering all DNS requests on the network, so users can't bypass eero Plus by changing DNS servers on their devices.
If you still want to change your DNS settings, you will need to first disable each eero Plus filter that's enabled. You can do this in the eero App:
- Tap the Home tab
- Scroll down, and tap the box below Security & privacy
- Tap Network Controls
- Toggle off Advanced Security and Ad Blocking. Remove any active Content Filters and blocked or allowed sites/apps from Block apps and Block & Allow Sites
Once all of these features are disabled, you will then be able to update your DNS settings.
What happens when I use custom DNS with other eero features?
Local DNS Caching
Local DNS caching works by storing DNS information locally, which speeds up webpage loading and access to other internet resources.
When this feature is enabled, you'll see the IP address of your Gateway eero provided to your devices instead of your ISP or custom DNS settings. This is required so devices can query the cached DNS information on the gateway.
The Gateway eero will send DNS messages to either your ISP DNS servers by default or to your custom DNS servers for resolution.
eero Hotspot Backup
eero Hotspot Backup lets you set up a nearby mobile hotspot or wifi network as a backup when your wired internet goes down. Once enabled on your network, your Gateway eero's IP address will be provided as the nameserver.
For more information see What is eero Hotspot Backup?
HomeKit
When the HomeKit feature is enabled, your devices will receive the IP address of your Gateway eero as their DNS server instead of either your ISP DNS servers or custom DNS servers, as this is required for HomeKit to function.
The Gateway eero will send DNS messages to either your ISP DNS servers by default or to your custom DNS servers for resolution.
For more information see How to use HomeKit with your eero Network
Ring Alarm Pro
One of the key features of the Ring Alarm Pro is cellular backup, so your network can fall back to using the LTE connection provided by the Ring Alarm Pro to maintain connectivity during an internet outage.
When a Ring Alarm is added to your network, either as the gateway or as a leaf node running v6.12.2 or higher, your Gateway eero's IP address will be provided as the nameserver.
For more information see About Ring Alarm Pro: Cellular internet
Using local DNS servers like RaspberryPi's with HomeKit, Local DNS Caching, or when using a Ring Alarm Pro device
When either HomeKit or Local DNS Caching are enabled, devices will send their DNS requests to the Gateway eero first. The gateway will then send DNS requests to your DNS server(s) for resolution.
If you're using a local DNS server, this may disrupt functionality based on what your local DNS server supports.
Some commonly used local DNS servers may have features that let the user gain insight into DNS requests by device or have other features that rely on DNS traffic being directly sent from devices on the network.
Since DNS traffic will be arriving from the Gateway eero instead of the devices themselves, most or all DNS traffic on your network will show as originating from the gateway. This means that your local DNS server may not be able to detect which device each DNS request is actually coming from.
This behavior can't be adjusted, as both HomeKit and Local DNS Caching require it to function properly. As a result, you may find that your local DNS server may not be fully compatible with these features.