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 ...
There is a small chance this thread might generate some interest to incorporate user-suggested features for future products. Or maybe even recently introduced products although doubtful. The company is small and risk adverse. I doubt they ever seriously consider new features on products that have already been released. And if they're like most tech firms, the sustaining engineering team is running well over 100% capcity just handling bug fixes and security patches. (Most consumer-facing tech firms seriously understaff their sustaining/support and quality groups - sad but typical and prone to outsourcing).
If there should arise a very highly requested feature, it has a better chance of making it into a future/new product. You can thank standard marketing 101 thinking for that - the mindset is to never give away value when you can charge for it. Instead, you put the value proposition into your next/new product to incentivize your customer base to upgrade. IMO, all the lamenting in this thread about not being heard just isn't going to change the way these businesses are staffed to run.
BTW the guy whose DNS lookups are taking 15s is clearly experiencing a bug/defect; that slow of a response is surely WAY outside the intended design parameters. Something there is amiss. Disabling the local DNS caching and simply forwarding the DNS server IPs directly to each LAN client would certainly workaround that bug. So I can understand why the guy latched onto this thread.