NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
newjoiner
Apr 24, 2026Guide
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...
newjoiner
Apr 25, 2026Guide
After your comment, I attempted the 3rd time with the latest firmware version, v1.0.11.6.
I discovered that I had set the custom DNS address to an invalid destination. Additionally, AdGuard Home is shut down, and the RS700S can still query for the DNS query.
e.g.: my network range is 192.168.1.0/24, and I set the primary DNS address to 192.168.2.1 or 192.168.100.1 or else.
The DNS leak test (https://www.dnsleaktest.com) shows the DNS request is forwarded to Cloudflare.
For the MITM part to investigating DNS steps, I may not go deeper since there are many services host in my homelab.
Instead, I will look deeper to the GPL source code.
any ads domain can test here >>> https://adblock.turtlecute.org
for example: afs.googlesyndication.com
=====================================
% dig 192.168.1.1 afs.googlesyndication.com
; <<>> DiG 9.10.6 <<>> 192.168.1.1 afs.googlesyndication.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51058
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;afs.googlesyndication.com. IN A
;; ANSWER SECTION:
afs.googlesyndication.com. 177 IN A 142.250.197.98
;; Query time: 5 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Sat Apr 25 20:41:42 HKT 2026
;; MSG SIZE rcvd: 70
FURRYe38
Apr 25, 2026Guru - Experienced User
So with v.11.6 FW loaded, the RS is working now with correct DNS configurations?
This was a mis-configuration of the settings?
- newjoinerApr 25, 2026Guide
RS always work, but the 3rd trial result indicates that may have DNS leak to other destination.
and seems not user-level mis-configuration of the settings.
However, since I rollback v1.0.10.8, just consider this case for reference only.
Thank you.