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 ...
@ schumaku I don't think you quite understand the issue.
I would have been happy with my ISP's direct IP being forwarded to all my devices. I would have been happy if the IP Address that I told the router to use would have been forwarded to my clients. What I'm not happy with is that the router itself is running a buggy DNS implementation.
I believe I may fall in with the "over-smart ISP" people that you're talking about, but I assure you, this request has nothing to do with security. In fact, the router is the backbone of a home network -- it's the most trusted device in the chain. The problem that I have is that the router allows you to enter a DNS server of your choice. When a client sends a DHCP request, the router is responding and providing the router's internal IP address instead of the one you provided.
Internally, the router is running a DNS server and anything it can't answer, it sends on to the IP address you define (or the one specified by your ISP in the initial DHCP request). There really is no problem with this, as long as the DNS server is robust enough to handle the requests. The netgear implementation is not.
Over time, the DNS service starts to get slow. Your internet appears to slow down, and just like the DNS Service, your internet suddenly stops responding. Again -- this apparently doesn't happen to everyone, but it's very easy to observe when it happens. Simply changing the clients DNS to an external DNS server resolves the issue.
This is an advanced networking device. It's geared towards power users and marketed at a premium price. The ability to modify the DNS server offered up when the client makes the DHCP request for it is not an unusual request.
While the lack of this feature doesn't, in itself, cause issues, the lack of an alternate method and an under performance DNS service does.
It's obvious netgear isn't going to resolve this issues, even though it was be very easy to implement as an optional setting that could default to their behavior.
There is a solution that they could use to make everyone happy...