NH20A router ignoring configured DNS forwarding — confirmed with AdGuard test
I've configured my NH20A router (logged in as admin) with specific IPv4 and IPv6 DNS addresses from AdGuard. After rebooting both the router and my laptop, I confirmed that the laptop receives the router's IP via DHCP for DNS resolution — so the router should be forwarding DNS queries to AdGuard, and clients should only need the router's IP in their DNS list. That’s the expected behavior. To verify this, I ran nslookup tests using domains that: Should not be cached by the router (never used before) Are known to be blocked by AdGuard DNS Here’s what I found: "nslookup domain AdGuard-DNS" returns NXDOMAIN or 0.0.0.0 as expected (AdGuard is blocking) "nslookup domain router-DNS" returns valid IPs, showing the router forwarded the query to Telus DNS instead of AdGuard This clearly shows that the router is not honoring the configured upstream DNS servers — it’s forwarding to Telus DNS regardless of my settings. Has anyone else confirmed this behavior? Is there a known workaround or hidden setting to force the NH20A to respect custom DNS forwarding?
Best setup moving forward
Moved houses and upgraded to 1 Gb PureFibre and brought along my T3200M with me. Already mounted on the wall in the new house is a Nokia ONT patched into an NH20A. I also brought with me a wired 4K PVR and wireless 4K STB which I need because my tv location has no wired Ethernet capability. Should I continue to use my T3200M or should i use the NH20A and ask Telus to provide me with a device to provide wireless in order to connect to my wireless STB?
