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 ...
Your needlessly combative and toxic response is a shining example of the Netgear Community.
I'm showing my support for a software change and justifying my interest by describing a problem I'm experiencing with a piece of hardware purcahsed new from a retail establishment in the last 30 days. Your "git gud" style bashing of this new netgear equipment in general seems amusingly out of place on community.netgear.com, and borders on being contradictory with your attempt to discredit my stated problem. Pick a lane. Is it that my problem is rubish or is it that the problem should be expected behavior because it's such a "low end" device? Who do you want to disparriage more?
As for my specific circumstance. This is new equipment running the latest available firmware and it's fair to assume it is "operating as designed". My contention is that if I had the ability to change which DNS servers are provided in the DHCP response, I would be able to effortlessly work around this problem I am experiencing.
user@localhost:~$ time nslookup google.com 192.168.1.1 > /dev/null
real 0m15.413s
user 0m0.006s
sys 0m0.005s
user@localhost:~$ time nslookup google.com 4.2.2.2 > /dev/null
real 0m0.091s
user 0m0.023s
sys 0m0.013s