NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RS700S new v1.0.11.6 DNS issue
After upgrading to version 1.0.11.6, my RS700S ignore my local AdGuard Home DNS response for blocking Ads. However, reverting to version 1.0.10.8 restored the functionality of my local AdGuard Ho...
Confirming this on 1.0.11.8 — with proof the router is force-forwarding LAN DNS to Cloudflare.
Same bug here on an RS700 running 1.0.11.8. My WAN DNS is set to OpenDNS (208.67.222.222 / .220.220), but no LAN device's queries actually reach OpenDNS — content filtering is completely bypassed. Here's hard evidence the router is ignoring the configured DNS and forwarding to Cloudflare instead:
- "dig CH TXT whoami.cloudflare 192.168.1.1" answers with my WAN IP. Only Cloudflare's 1.1.1.1 responds to that query, so the router is clearly forwarding there.
- "dig TXT debug.opendns.com 192.168.1.1" is empty. That query returns diagnostics only when it actually reaches an OpenDNS resolver, so my queries never get there.
- 15 of 15 test queries through the router failed to reach OpenDNS.
- Querying OpenDNS directly (@208.67.222.222) blocks correctly — so my account and settings are fine. The break is purely the router refusing to route devices to the DNS I configured.
This matches what others here report: 1.0.10.8 honors custom DNS, 1.0.11.6 and 1.0.11.8 do not. It affects both IPv4 and IPv6, even with IPv6 disabled. There's no setting that overrides it — the LAN page won't hand custom DNS to DHCP clients, and the built-in OpenDNS parental-control page is non-functional (its backend returns 404 on this firmware).
For anyone stuck: downgrading to 1.0.10.8 is the only working fix right now.
NETGEAR — can we get an acknowledgment and a firmware fix? Custom DNS at the router is a core feature, and it's been broken across two releases. Silently overriding it with Cloudflare also has real privacy and parental-control implications. Happy to provide logs or test a beta build.
You'll need to contact NG support and submit a report/logs there.
Cloudfare isn't a bad DNS as an alternative. Though yes I agree, there should be user configuration to change the 3rd DNS entry that is currently hidden in the WEB UI.
Again, make contact with NG support regarding this. We've already passed this to NG for review.
Confirming this on 1.0.11.8 — with proof the router is force-forwarding LAN DNS to Cloudflare.
Same bug here on an RS700 running 1.0.11.8. My WAN DNS is set to OpenDNS (208.67.222.222 / .220.220), but no LAN device's queries actually reach OpenDNS — content filtering is completely bypassed. Here's hard evidence the router is ignoring the configured DNS and forwarding to Cloudflare instead:
- "dig CH TXT whoami.cloudflare 192.168.1.1" answers with my WAN IP. Only Cloudflare's 1.1.1.1 responds to that query, so the router is clearly forwarding there.
- "dig TXT debug.opendns.com 192.168.1.1" is empty. That query returns diagnostics only when it actually reaches an OpenDNS resolver, so my queries never get there.
- 15 of 15 test queries through the router failed to reach OpenDNS.
- Querying OpenDNS directly (@208.67.222.222) blocks correctly — so my account and settings are fine. The break is purely the router refusing to route devices to the DNS I configured.
This matches what others here report: 1.0.10.8 honors custom DNS, 1.0.11.6 and 1.0.11.8 do not. It affects both IPv4 and IPv6, even with IPv6 disabled. There's no setting that overrides it — the LAN page won't hand custom DNS to DHCP clients, and the built-in OpenDNS parental-control page is non-functional (its backend returns 404 on this firmware).
For anyone stuck: downgrading to 1.0.10.8 is the only working fix right now.
NETGEAR — can we get an acknowledgment and a firmware fix? Custom DNS at the router is a core feature, and it's been broken across two releases. Silently overriding it with Cloudflare also has real privacy and parental-control implications. Happy to provide logs or test a beta build.