NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
DNS Error Popup Issues (Round 2)
Using the NETGEAR Orbi RBK852 AX6000 mesh router, since purchased, with various firmware versions (no other routers I've used in the past have this problem) Now currently on Firmware Version v4....
Possible fix:
NAT Filtering > SIP ALG
NAT Filtering is set to Secure and has a tick box to disable SIP ALG upon it checked by default. Unticking that and enabling SIP ALG appears to of improve it's performance, creating a snapper response to device calls and may have of resolved my DNS issue too.
Will mark this as resolved, once fully tested and confirmed.
ONT = Chorus Optical Network Terminal Model Type 200
It doesn't have Wifi features or any setup options I can access. It appears to have it's own flat cable of a CAT 5E type, I've used that to connect directly to the Orbi Router. Set as Router Mode.
The Orbi Router then has a CAT 6 cable directly to a desktop PC. Only that device is connected to the main router.
Other Satellites connected to the TV, Nvidia Shield Pro and other various devices will use CAT 5e Patched ethernet cables.
I have Armor and SPC both disabled. UPnP is also disabled.
I have VLAN enabled and VLAN tag group set ID = 10 on all Wired Ports and Wireless. This is required by the ISP.
I use IPv4. IPv6 is disabled as my ISP doesn't support it. I did previously use a 6to4 Tunnel for IPv6 and that solved the DNS issues from appearing, however Google Search Engine warned it was insecure and being discontinued. So gone back to IPv4. Hense why I bring it up again (Round 2).
Validus wrote:
ONT = Chorus Optical Network Terminal Model Type 200
It doesn't have Wifi features or any setup options I can access. It appears to have it's own flat cable of a CAT 5E type, I've used that to connect directly to the Orbi Router. Set as Router Mode.
The Orbi Router then has a CAT 6 cable directly to a desktop PC. Only that device is connected to the main router.
Other Satellites connected to the TV, Nvidia Shield Pro and other various devices will use CAT 5e Patched ethernet cables.
I have Armor and SPC both disabled. UPnP is also disabled. Would you enable uPnP please let see if this changes anything. After enableing this, do a full power OFF of the ISP ONT and RBR for 1 minute then back ON.
I have VLAN enabled and VLAN tag group set ID = 10 on all Wired Ports and Wireless. This is required by the ISP.
Wondering if this maybe a factor here as I don't use this for my ISP and I have not seen any DNS issues whatsoever. Possible that mis-handling between the RBR, this vlan configuration and the ISP ONT could be at play here.
I use IPv4. IPv6 is disabled as my ISP doesn't support it. I did previously use a 6to4 Tunnel for IPv6 and that solved the DNS issues from appearing, however Google Search Engine warned it was insecure and being discontinued. So gone back to IPv4. Hense why I bring it up again (Round 2). After testing with uPnP enable and if you don't see any change, please re-enable this as a short term test to see if this problem continues or is resolved by using 6to4 DNS configuration.
Lets see if any of these two items change the DNS behavior. I believe that probably that your ISPs VLAN configuration and how the RBR is handling it maybe the problem as you say, this has been happening on every FW versions, this leads me to think that something in this configuration is not working right. We may need you to capture debug logs for NG review.
Thanks for the suggestions. I'll try one thing at a time and allow for testing each change.
Firstly I have removed the entries under the HOST file. There was a ton pointing to 0.0.0.0 or 127.0.0.1 to block out due to Spybot. It was 460KB and now is 1KB.
After quite some time today, got the same results as before from the URL:
https://home.nzcity.co.nz/tvnow/tvguide.aspx
It popped up with the message "ERR_NAME_NOT_RESOLVED" again, then refreshes and loads fine. However this time, there was no failed/blocking of Request URL: https://www.google-analytics.com/urchin.js
Instead it just shows two HTTP Status 499 instead...
Request URL: https://secure-nz.imrworldwide.com/v60.jsRequest Method: GET
Referrer Policy: strict-origin-when-cross-origin
cache-control: no-store, no-cache, must-revalidate, max-age=0Those will remain the same doing that, unless I visit the URL directly. Is that normal? I think my system just loves to block ads and trackers. Still wondering if it's related or just confusing me on were the root cause is?Can rule out the HOST file from being the issue so far.What browser are you using? This happens across other browsers and other PCs?
Web-browsers: Microsoft Edge, Firefox, and Google Chrome
Happens on a desktop PC directly connected to the Router and a laptop using wifi from one of the Satellites.
It's rare when it decides to happen but can happen a lot during that time period. Feels like if someone is exploiting the Orbi router for DDOS attacks or something like that? Perhaps happens when streaming either Netflix across the Nvidia Shield, Steam downloading a huge game, or using multiple web-browsers (Edge + Google Chrome) at the same time streaming Youtube? So maybe to do with hogging the bandwidth or multiple devices using it at the same time. Then when you google or open a certain webpage, it will only occur on certain ones, most commonly when there's a redirect such as this website going to the login or logout. Checking Yahoo emails, logging out. Yet also sites like going directly to that NZCity TV Guide URL as mentioned in the previous post.
Been trying to narrow this issue down for a while now but appears to just of temporary masked it.
Another curious thing that occurs is when there is a firmware update, it seems to be working well for a week or so. Progressively getting worst over time. I know it doesn't seem to affect IPv6 at all, only IPv4.