NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
R9000, All DHCP clients are receiving the wrong DNS IP (The Router)
I have entered the IP address I want the LAN clients to use but all the wireless devices get 192.168.1.1 (the router). I can find no way to fix this.
This is the behavior for all NG routers. The proxy hands over the routers IP address, however when DNS get to the router and if you have different DNS configured, then it goes out thru those addresses. How it works on NG routers. Been like this for a LONG time. If that's not working for you then you'll need to find an alternative to NGs stock FW. Or find a different brand. One brand I know that users can disable this proxy and the router hands over what ever DNS is configured to any connected devices is D-Link routers. They call theres DNS Relay.
I am not looking to do away with the proxy, I really don't care. But the problem I have is that that proxy IP is being handed to my internal wireless clients even though I have configured it to give out my internal LAN DNS IP's. It seems to be ignoring the configuration entries. This is unacceptable. In the hundreds of environments I have been in that have DHCP servers, all of them give out the IP they are configured to give out. Not whatever the engineers have designed it to give out.
Why even have the ability to enter DNS IPs if it won't use them? I'm astounded that this made it to production as it is NOT what it appears it should be doing.
This is the behavior for all NG routers. The proxy hands over the routers IP address, however when DNS get to the router and if you have different DNS configured, then it goes out thru those addresses. How it works on NG routers. Been like this for a LONG time. If that's not working for you then you'll need to find an alternative to NGs stock FW. Or find a different brand. One brand I know that users can disable this proxy and the router hands over what ever DNS is configured to any connected devices is D-Link routers. They call theres DNS Relay.
Okay, I have thought about this quite a bit. My issue is not that the router does DNS on it's IP. Does not bother me at all because I don't want to use it and don't care if it does it regardless.
It is that the GUI provides for sending DHCP clients a different DNS IP. When the fields are filled in and the router rebooted. It does not send the requested DNS entry(s) to the clients. So if it is incapable of sending the requested IP's why offer a provision to provide different ones that cannot possibly work? Isn't that kind of misleading? (A bold faced lie). Netgear as a company is better than that. I still want to think so. This is getting entertaining, I think a post on Reddit or Slashdot or both is a good idea. I think the public might agree with me.
Again, the NG router is a proxy for DNS. The proxy IS 192.168.1.1 for ALL DNS services up and to the router. This gets passed to any and all connected clients on the client side. When it hits the WAN side and what you have configured in the DNS settings, is when it changes over to what you have set there. WAN side to router. Been like this with NG routers since forever. So no lying. Probably not understanding how NG routers work.
Something to check out since this router is EoL, check on Voxels FW. What I have loaded on mine, though I don't use it much anymore or if I do, wireless bridge mode. He keeps his FW more up to date for the R9000 series. Maybe you'll find what your looking for there.