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
Absolutely agree!
- Please provide an update for this. I'm considering standing up another router to do DHCP so I can provide an alternate DNS server to my DHCP clients.
Please! This feature would make my network way easier to administrate (other than replacing my Netgear router with a differernt one)
- I would like to see more flexible DNS features for NGs router and give some DNS control to there users. DNS relay being one of them. It would be nice to disable or enable DNS relay where needed. Other non-NetGear routers can do this. Would be nice if NG routers can as well. Please.
The lack of this feature caused me great difficulty wirth orbi DNS features. please add
Really need this feature it makes total sense.
Folks, don't forget to click on the up arrow.
Please add or fix DNS feature on R8500. I have several dozen Netgear devices in my house. I upgraded from the R7900 that worked with local DNS. I replaced my netgear router R7900 with the R8500 (Which might be my last). I was not expecting that my local DNS would stop working with a device that costs almost twice as much. I have tried everything except going to WRT's version of code. My NAS's DHCP breaks some IOT devices, so had to go back to DHCP on R8500 if I want to use those devices.
This feature should be available if you intend to market your devices to power users. Frankly, if I had knew this wasn't possible beforehand, I would have purchased a product for your competitors which does support this simple feature...
This seems like an obvious feature.
I have an R6400 with updated firmware and it still doesn't seem to relay AAAA requests for IPv6 addresses. Unfortunately, I can't disable the relaying without disabling DHCP on the router and running a separate DHCP server.
This problem is compounded by the inconsistency with which my Windows 10 laptop receives IPv6 DNS servers specified in the router configuration. Upon connecting to the WiFi network, it seems to be entirely random as to whether or not the specified IPv6 DNS server or the router's IPv4 address is used. I'd guess this is a conflict between DHCP on IPv4 and autoconfiguration on IPv6 but if the if DNS relaying worked properly or if I could disable relaying entirely, it shouldn't matter much whether my DNS requests are over IPv4 or IPv6. As it stands now, I get 30+ second lags while waiting for AAAA DNS requests to timeout (literally no response at all from the router when observed with wireshark) followed by the connection failing over to IPv4.
For now, the workaround is disabling IPv6 entirely but that certainly shouldn't be necessary.
