NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Two requests:
- Add an option to toggle whether the router advertises its own IP address as a DNS server. Advanced users don't need routerlogin.net.
- Allow a private IP address to be specified as a DNS server. This currently doesn't work because the DNS relay occurs after NAT. A user has to disable the DHCP server on the router in order to use their own DNS server.
89 Comments
For the IPv6 lookup I've seen this issue in various enterprise customer environments with other routers where the IPv6 DNS doesn't respond and we have to set the Java server environment to run with preferIPv4 on the command line.
Agree with all others Netgear should implement fixes so we can control our own DNS servers. Upvoted.
- Status changed:UnspecifiedtoReviewed
- I would also like to see this feature implemented. I use a Pi-Hole as an internal DNS server in order to block ads, and have configured my Nighthawk X8 R8300 with the Pi-Hole as the primary DNS server. The issue I see is that the DNS request logs on the Pi-Hole now indicate that every request comes from the router instead of the specific computer/device. Thankfully the Pi-Hole is also capable of being a DHCP server, which will resolve this problem for me.
- I also have Pi-Hole and had to set it up to be the DHCP server. But it makes the configuration more complex than it needs to be. I hope Netgear fixes this.
- Another vote for this option. I'd prefer to use my pi-hole to provide DNS.
I agree this should be an option. And in general, more options for the DHCP server (lease time, separate subnet ranges for the guest wifi, etc).
I have an R7000 and the internal DNS is often (>1/month) unresponsive. Perhaps because I have >70 devices, half of which come and go and most of which will be utilizing the DNS.
So that I do not have to reboot the router, or teach my family when and how to, I would like my router's DHCP server to issue the IP of DNS servers that I specify rather than its own internal DNS. I do not require any make-it-easy behaviors so placing this configuration option in Advanced Settings would be appropriate.
Yes, I know I can set up my own DHCP server and I have done that in times past. But, now I have to travel more frequently and need to maximize the availability of my home's basic infrastructure. One of the most common failures when I am away from home is now that R7000's DNS server stalling out.
Hard-configuring a device's DNS list fixes the issues I see for service from that device, but many of my devices need to register with multiple networks through the week and in any case maintaining all those devices with the same DNS becomes cumbersome.
Thanks!
Please, add this feature. We can improve DNS lookup performance if our clients did "direct" DNS lookups rather than using Orbi as DNS (proxy) lookup. I tested performance of direct client DNS lookup queries to quad nine DNS service (9.9.9.9) against Orbi DNS lookups to the same 9.9.9.9 service. Used GRC DNS Benchmark software.
Uncached dot com latency: Orbi=81ms, direct lookup=41ms
Cached query latency: Orbi=41ms, direct lookup=6ms.
This DNS lookup degradation can be worked around using the "direct" method, where Orbi doesn't advertise itself as DNS server - but instead passes along those defined by the user (if specified), or the one obtained from the WAN DHCP (i.e. the service provider).
- I gave up. Switched off the DHCP on the Netgear, and shuffled it over to a Pi-Hole running FTLDNS. It was just easier than continuing to deal with it, at this point.
- This is common feature used by many. What was Netgear's logic to not include the feature?
