NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
How to get Orbi to pass through DNS information in DHCP?
I have an Orbi RBR50 running Firmware Version V2.5.1.16. I'm using its DHCP feature. The problem is that no matter what settings I try in the configuration, it always hands out client leases with the...
Orbi DHCP server isn't broke in regards to handing out it's router IP address for all clients DNS. Thats just how NG designs there routers to work. NG seems to have had this design for a long time standing up to this point on there router products.
If you want the ability to disable DNS proxy, the one Mfr that has this option feature is D-Link. There routers allow for disabling of DNS proxy on there router. It's call DNS Relay for them. Something you could try and find a used D-Link router and set one up as your main host router and test it out. Can connect the Orbi in AP mode behind the router as well.
SunriseMan wrote:
Mstrbig wrote:The router's DNS server is an internal server. The Orbi uses the ISP or user provided 3rd party DNS servers, such as Google, Level 3, Open DNS, etc.. DNS over HTTPS server implementations are already available free of charge by some public DNS providers.
That wasn't my question.
A DHCP server gives DNS addresses to devices. Orbi's DHCP server is broken and always gives the router's address as the DNS address. So my Windows computer thinks that the DNS address is 192.168.1.1, rather than the address I configured.
I use a service that supports DoH. But Windows (again, for now I'm talking about the Insider versions, but this will soon be true for release versions as well) detects that by just trying to do a DoH request. And that will always fail, because the Orbi doesn't support DoH.
I'm not expecting the Orbi to support DoH. But its DHCP server should be able to correctly pass along the correct DNS servers rather than incorrectly giving its own address.
FURRYe38 wrote:Orbi DHCP server isn't broke in regards to handing out it's router IP address for all clients DNS. Thats just how NG designs there routers to work. NG seems to have had this design for a long time standing up to this point on there router products.
Broken by design, and broken by design for a long time, are still broken.
The DHCP spec calls for the IP addresses specified in DHCP to be passed to the client. Orbi does not do that. i.e. it is "broken".
FURRYe38 wrote:
Well thats your opintion of course.
It is also the opinion of the IEFT who drafted the DHCP spec, and the vast majority of professional network engineers.
FURRYe38 wrote:
Orbi is mostly simplistic towards the average home user. Same with D-Link. More advanced users may want to get into something with more advanced features for those needs.
This statement is ridiculous.
DHCP was designed explicitly for ease of use. DNS is a core function of DHCP. Specifiying a DNS address is part of DHCP.
In stark contrast, VPN, reserved IP addresses, channel freequency assignment, et.a. are all features for advanced users. And they are present in Orbi.
DNS config in Orbi is fundamentally broken. Stop justifying bad design/code.
Router Mfrs don't have to follow that spec and from long standing design, NG doesn't. Been like this for years. Even my WNDR3700 back then wasn't able to turn OFF DNS Proxy.
Looks like PiHole is your alternative.
Good luck though.
FURRYe38 wrote:Router Mfrs don't have to follow that spec and from long standing design, NG doesn't. Been like this for years.
Year after year, two things never change:
1) Netgear continues turning out garbage code.
2) FURRYe38 continues turning out garbage posts.
FURRYe38 wrote:
Even my WNDR3700 back then wasn't able to turn OFF DNS Proxy.See #2 above. DNS proxy isn't even the topic of discussion.
DNS Proxy/Relay is what NG uses (192.168.1.1) or the router IP address/gateway, when it shows up on the client side when connected to any NG router. Same thing as DNS Relay. On some other Mfr routers like D-Link, which users are able to disable DNS Proxy/Relay and there devices get the actual DNS detected by the host router or any custom DNS the user inputs in to the router. NG doesn't seem to want to support this. They may have there reasons. There product, there design. Don't like it, find something else.
I agree that users should have the choice. Not saying other wise. Just saying is all that NG hasn't moved on this on there router line ever and has been so long, NG doesn't seem to wanna budge. By all means though, keep asking though. You might post here about it though:
https://community.netgear.com/t5/Idea-Exchange-For-Home/idb-p/idea-exchange-for-home
Good Luck.
OrbiPhilip wrote:It is also the opinion of the IEFT who drafted the DHCP spec, and the vast majority of professional network engineers.
Would be helpful to see the section of the DHCP standard that discusses Option 6. I have looked at RFC 2131 and RFC2132 without much success.
Personally, I am on the side of, "Let the user choose." It appears to me that Netgear follows the same practice as Windows: the user can choose to (a) accept the DNS servers offered through DHCP, or (b) define other DNS servers. Does not seem to be very complicated to add another choice: provide the gateway IP as the only DNS server or some specific IP's as DNS servers.
