DNS Error Popup Issues (Round 2)

Spoke too soon, it occurred once again during the logging out of this site. Now to try capture it, because it doesn't occur twice in a row on the same thing, unless I clear out the cache (using CCleaner app).

---

Validus wrote:

I'll try to capture it when it happens. It's hard to time and record or recreate it. Currently it's working fine again.

 

Last night and this morning it didn't occur at all, yet nothing else was also using the connection to stream or download. Steam has finished all it's game updates too. I suspect it's either multitasking or bandwidth hog requirement for the issue, unless there's something changed on Netgear's server side since I mentioned it with DNS lookups?

 

If the Netgear Armor is turned off, does the DNS lookups still go to it's server? We've seen Armor cause some problems, even after it's been disabled. Why we ask if it's ever been enabled, if so, we ask the you factory reset and setup from scratch. This seems to clear out any lingering Armor backend code from running, even after it was disabled. 

 

Or doesn't the router hand out DNS calls to multiple devices using it at the same time, without actually knowing what device called it? Like with the routing table or timing out if busy with other things?

 

So far I've just wiped the HOST file and recreated it again with the Spybot Immunity.

---

If you can capture the debug logs from the RBR, post them up on a cloud site like dropbox or something that you can send me the shared file link in a PM. 

Might try that factory reset on all (router and each of the satellites). Might be onto something and worth a try. I have performed power cycles with each firmware upgrade but not a full factory reset. This problem seems to of improved each firmware update, but still tailed around. So it could of been settings from an older version still remaining behind?

Before I do that, just checking my IPS setting requirements, it wants the following...

Operating mode: MDI/MDIX
PPP protocol: PPPoE
PPP auth type: PAP
PPP mode: Always on (dial on demand disabled)
Encapsulation: 802.1Q
PCP marking: 0
VID (or VLAN): 10
MTU: Auto or 1500

I'm not sure were to set the Operating mode as MDI/MDIX on the Netgear Orbi? Is this something I need to worry about or can ignore? Same deal with the Encapsulation and PCP marking?

Currently the settings on the Router are as follows...

Set to Router Mode

MTU size: 1492

NAT Filtering: Secured

Under WAN: IGMP Proxying is set to disabled (is this any problem, I'm wondering if it should be enabled?)

RIP Version: Disabled

Use Router as DHCP Server

Preferred NTP server: nz.pool.ntp.org

UPnP: Disabled
IPv6: Disabled
VLAN: Enabled (by VLAN tag group) VLAN ID: 10

Web Services Management: Always use HTTPS to Access Router

---

Validus wrote:

Might try that factory reset on all (router and each of the satellites). Might be onto something and worth a try. I have performed power cycles with each firmware upgrade but not a full factory reset. This problem seems to of improved each firmware update, but still tailed around. So it could of been settings from an older version still remaining behind? Possible.

 

Before I do that, just checking my IPS setting requirements, it wants the following...

Operating mode: MDI/MDIX 
PPP protocol: PPPoE
PPP auth type: PAP
PPP mode: Always on (dial on demand disabled)
Encapsulation: 802.1Q
PCP marking: 0
VID (or VLAN): 10
MTU: Auto or 1500

 

I'm not sure were to set the Operating mode as MDI/MDIX on the Netgear Orbi?  Is this something I need to worry about or can ignore? Same deal with the Encapsulation and PCP marking? <Unknown possible automatic with Orbi.

 

Currently the settings on the Router are as follows...

Set to Router Mode

MTU size: 1492 <What required by the ISP?

NAT Filtering: Secured< You can try change to OPEN and see if the changes anything if not, change it back.

Under WAN: IGMP Proxying is set to disabled (is this any problem, I'm wondering if it should be enabled?) < You can try change to OPEN and see if the changes anything if not, change it back.

RIP Version: Disabled<Ok however DIRECTION maybe BOTH.

Use Router as DHCP Server

Preferred NTP server: nz.pool.ntp.org< Try setting default NG server.

UPnP: Disabled< Enable this please
IPv6: Disabled
VLAN: Enabled (by VLAN tag group) VLAN ID: 10

Web Services Management: Always use HTTPS to Access Router< Any differences seen if you disable this?

---

I made a typo in the previous post, IPS setting requirements was meant to be ISP (Internet Service Provider).

So they want MTU: Auto or 1500 (the Netgear Orbi has automatically set it as 1492, but seems fine I think)

I have currently just toggled the IGMP Proxying. Enabling that seems to of helped. I use a lot of IPTV and Netflix streaming across to the TV with a Nvidia Shield Pro. So I think that's smoothed out the load on that?

I was about to do the factory reset, but haven't had the DNS issue popup yet. Holding off to test one change at a time.

I've already tested Web Services Management: Always use HTTPS to Access Router, there's no difference if that's toggled on or off. Just that the URL //192.168.1.1 doesn't automatically redirect to https://192.168.1.1 before asking for the admin login. So it actually asks you to correctly login twice if using that.

Preferred NTP server has also been tested, changing that doesn't affect it.

DNS issue occurred once more, when two devices were running - Nvidia Shield Pro streaming IPTV and the desktop PC wired browsing the Internet via Microsoft Edge. Happened on a news webpage never visited before for just a split second.

So I factory reset the router.

Just a note about the Netgear Orbi App router setup, in regards to the Internet connection...

With the factory reset, it wanted to use the Netgear Orbi App. However, when it gets to the connecting to the internet stage of that app, it will end up in an endless cycle of checking. I suggest the app should ask firstly if you want to automatic detect or have manual settings. The advanced settings option doesn't have the VLAN setting which my ISP requires to connect.

I went desktop instead with a wired connection to setup the router. Same deal, will setup Satellites and the Wifi, but not connect to the Internet. Can bypass it into the advanced settings and once VLAN is set, it connects and works fine.

Everything is up and running again. UPnP is also currently enabled.

The DNS issue happened as soon as visiting the URL: https://www.google.co.nz/

Once the website is cached, it works fine every time. It's just non-cached webpages affected.

I did test Wifi devices before that, such as the Nvidia Shield Pro connecting to IPTV and my cellphone connection, etc.

Went back to the Netgear Orbi App and noticed some of the Wifi devices are incorrect. Like old leftover ones, some using the same name as other devices. Each of them had the IP Address: 0.0.0.0. So delete those from the list and cleaned up the Wifi device names. I wonder if that app messed the setting up before?

I'll flush the Desktop's DNS as well, just incase.

Sounds like the VLAN setup is needed during the setup phase for the setup app or orbi app to correctly complete. I guess you'll need to keep this in mind. 

Seems like un-cached sites/DNS shows this. I'll add this information to this bug report I posted. 

Fingers crossed might of finally fixed this DNS issue!

The factory reset and resetup of the VLAN seems to of worked well after the DNS Flush. There's been no issues since then.

UPnP I've disabled again, as I consider it a bit of a security risk

IGMP Proxying is enabled as that seems to help with streaming content

Manually cleaned up the Netgear Orbi App Wifi device list as well

I think it was mostly leftovers from the older firmware or first setup of the VLAN?

Otherwise, there was a bunch of blocks in the HOST file which even included blocking Google Analytics on webpages, leading to that error message which the entire page would display for a few second.

Soon after that I had noticed was a Websocket Status 101 - Switching Protocols...

Cache-Control: no-store, no-cache, must-revalidate, max-age=0
Connection: Upgrade
Content-Length: 0
Upgrade: websocket
Stalled

CAUTION: Request is not finished yet!

Not quite sure what that meant, but it's no longer occurring anymore. Has all been heavily tested now, but will reconfirm if resolved after a week or so usage.

Thanks for all your help FURRYe38 

Ok, let us know how it goes. Hoping something go blown out and DNS starts working better for you. 

Keep an eye on that host file. Should not be lots of entries in there. Only some necessary ones that you or some specific app may have setup. 

If uPnP isn't needed then it's ok to disable. uPnP issues were resolved years ago. I've not seen any uPnP issues as I keep it enabled on my router, though I game online so I need it. 

Be sure to save off a back up configuration to file for safe keeping. Saves time if a reset is needed.
https://kb.netgear.com/000062080/How-do-I-back-up-the-configuration-settings-on-my-Orbi-WiFi-System

The DNS Error issue might still be there, but whatever triggered it has been greatly reduced. It almost doesn't happen at all anymore and is no longer a hassle for me.

Narrowed it down to the possible following requirements to trigger:

- IPv4 only (IPv6 is unaffected)

- VLAN 10 (?)

- Webpage with a script blocked on it via 0.0.0.0, either with an ad blocker, anti-virus, or the HOST file (HTTP STATUS blocked:other  isn't affected by it, rather needs to be status = net::ERR_NAME_NOT_RESOLVED or similar DNS error warning)

- An URL redirect or multiple webpages loading (it could be triggered by half loading a webpage, then quickly going to another, or perhaps using IPTV, Netflix, or Youtube streaming on a device, while going to a webpage on another)

- No DNS cache on those webpages (as soon as it's cached it will work fine every time after that)

- IP Address change might also trigger it (?)

What occurs is it's getting the valid error message from the script called/blocked on the webpage, but displays it over the entire webpage, then refreshes and loads the webpage as normal. There could be a slightly delay/hanging during this before the DNS error is displayed. The refresh is quite instant.

This only ever occurred on the PC and Laptop, never other devices such as the Smartphone while web-browsing on them. Both of those had Spybot originally installed with it's immunization and Spybot Anti-Beacon, which added blocks into the HOST file. Kaspersky Internet Security ad-blocker was also another cause of similar blocking which triggers this issue. It's just due to the way they block scripts on webpages with the Netgear Orbi Router react towards.

It is not affected by:

- uPnP

- IGMP Proxying (those this did help a lot, smooth out the large amounts of steaming -IPTV, Netflix and Youtube)

- Always use HTTPS to Access Route turned on or off

- Adblockers which use blocked: other as the HTTP Status

Hope that might help, if any others have similar issues.

Any updates on this? 

FYI, there is new FW out in the wild...

Validus 

FURRYe38 I was still getting some random webpages displaying "Err_Name_Not_Resolved" before (few second displaying that message, then reloads the webpage normally).

My router and satellites appear to of been updated to version 4.6.8.2 automatically now. However, appears to of done so smoothly. Will see how it goes.

So far since firmware version 4.6.8.2 and a DNS flush, there has been no issues at all. I didn't even need to reboot the router. I don't want to jynx it but looks hopefully fixed!

Ok. Kewl. Lets give it 3 days and then let us know your findings.