NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RBK50 DNS problem
I have Orbi system RBR50 + three RBS50 wire connected, all devices has latest firmware (2.3.1.60). About 5 clients connected by wire and 10 wireless clients. Internet connection PPTP. There is a pr...
Michael50 wrote:If I manually change clients IPv4 settings router's DNS 192.168.1.1 to provider's DNS 10.1.1.1 or Google's DNS 8.8.8.8, the problem is solved.
This probably has nothing to do with the issue, but if the provider's DNS is 10.1.1.1, that it likely an indication that you have two routers (a "double NAT"). Although it works "most of the time", there are specific situations where applications fail miserably.
Seems like yet another case of going back to basics.
We have a user who wants to change settings to deal with a perceived issue.
It might be better to tell people what that issue is and then they may have ideas on how to deal with it without having to change those settings, especially when they are "impossible".
Getting stuff to work is the important hit and there may be many easier ways of doing that.
Knowing the problem and the rest of the stuff on the network, especially the make and model of the modem, would be a good start.
My problem is hanging DNS Proxy on router, it cannot handle multiple requests.
Is there anyone here who has a connection with firmware programmers to fix this problem?
Just to clarify: the issue is that web pages load slowly when the Orbi is acting as the DNS (192.168.1.1), and web pages load at normal speed when the DNS is anything else, including the ISP gateway (10.1.1.1) or Google (8.8.8.8)
While investigating the problem, it was observed that "nslookup" queries would time out. Since nslookup is a form of DNS query on port 53, the conclusion is that Orbi's DNS processing is defective. Thus, the desire to have Orbi use DHCP to inform devices to send DNS queries to someplace besides Orbi.
One solution would be to put Orbi in AP mode, which means devices will get DNS of 10.1.1.1. The "downside" to this is probably that the user cannot configure the ISP device and thus will lose all Orbi router functionality.
CrimpOn wrote:One solution would be to put Orbi in AP mode, which means devices will get DNS of 10.1.1.1. The "downside" to this is probably that the user cannot configure the ISP device and thus will lose all Orbi router functionality.
Or manually modify DNS server on clients, but it is a duct tape.
Maybe someone can report this DNS error in bugtrack?