08-03-2016 06:52 PM
I have been running with OpenDNS for over a year now and nothing on my local network has changed that I am aware of. Over the last few weeks the internet connection has been VERY patchy. One moment fine, the next NOT. Sometimes I have one browser session working (e.g. streaming video) whilst a new browser session can't connect to anything. The Web interface to the router sometimes reports the internet is down even whilst I am streaming data! I can be on standard sites and sometimes the images don't fully load (little crosses are displayed in place of images). This usually happens after the link is unavailable and it hasn't fully recovered. Sometimes I get complete outages and no browser sessions work. Then a few minutes it all comes back but only lasts a few minutes. It's very disruptive.
I found by changing my router primary and secondary DNS settings to my ISP's settings everything works reliably. However that means I have to turn on parental (OpenDNS) controls. The OpenDNS primary and secondary DNS settings are 208.67.222.222 & 208.67.220.220. I am based in Australia and using Optus cable internet.
I would really appreciate some help as I want to keep the level of protection for my kids that OpenDNS provides but at the moment it is causing terrible connectivity issues.
08-09-2016 01:00 AM
Yes, that's most likely the case since the diagnostic results indicated that your IP address was registered to an OpenDNS account. If you didn't have a network associated with your account, then the network must have been associated with someone else's account, which would certainly lead to unexpected filtering results.
08-09-2016 01:16 AM
Thanks Matt. What in the diagnostic is stating 122.107.216.203 is registered with OpenDNS network ID 27456154.
I can see this in the diagnostic output but not sure what it is saying. Does originid mean that belongs to OpenDNS?
"originid 27456154" debug.opendns.com text = "actype 1"
debug.opendns.com text = "bundle 27456154"
My internet service is now working more reliably (I assume because the public facing IP allocated to me by my ISP is talking directly to OpenDNS DNS servers). As recommended I opened a ticket with OpenDNS a few days ago.
08-09-2016 08:26 AM
Folks, I am further convinced that the two products can work together and are designed to do so. At the top of the OpenDNS dashboard stats page there is a link http://netgear.opendns.com/ that is called "manage your NETGEAR device" and it shows the LPC settings as I described earlier i.e. the filtering level and exclusion times etc.
Comments?
08-09-2016 09:13 PM
Just because two different products share some of the same infrastructure (such as DNS server addresses or account login credentials) does not mean they are complementary or can work together.
LPC and OpenDNS most definitely were NOT designed to work together. There are many years of messages in which OpenDNS employees have posted in this forum where they state that the two products are not compatible, and that you have to choose which one you want to use, and then completely decommission the other one. No one here is going to tell you otherwise, or provide any support or advice in getting the two to work together.
08-10-2016 01:54 AM
Matt I appreciate what everyone is saying but I have no information from anyone saying "how" I am supposedly using OpenDNS? This is the key question.
I temporarily just setup OpenDNS and switched off LPC and everything is stable. I wish to switch back to LPC so apart from deleting the network I have defined what else is required? I can see there are tick boxes selected in the various dashboard settings (probably as a default to the network I temporarily setup). If when removing the network these boxes don't clear themselves should I also untick them? e.g. collect stats, dynamic update enabled, phishing protection
Lastly, I just received a response from the OpenDNS ticket regarding
"The IP address you submitted has been registered to you and there was no other OpenDNS client using this IP address (122.107.216.203)."
So the suggestion from Rotblitz (below) has been discounted
The problem seems to be that your IP address 122.107.216.203 is registered with OpenDNS network ID 27456154. So the settings of this dashboard network may take precedence over your LPC settings and ignoring the latter. Your IP address information may be registered by another OpenDNS user, so you want to open a support ticket to get this removed
08-10-2016 04:18 AM
Delete the network you have setup on the OpenDNS dashboard. Remove any other settings you manually added anywhere. Reenable LPC. I'm done with this thread so if you have any other issues I suggest opening a ticket with OpenDNS.
08-10-2016 10:36 AM
"So the suggestion from Rotblitz (below) has been discounted"
OpenDNS' response rather indicates that my suggestion holds true. I raised it two days before, and a lot can change regarding IP address assignments during two days.
Definitely, at this time (on Aug 7) your IP address information was registered with another OpenDNS network. This user may have run another update in the meantime which freed up your IP address information.
08-10-2016 07:00 PM
I've been having the same problem as the original poster. I do not have a Netgear router. I have my Century Link provided router with no child controls enabled (it has none). Over the last couple of months, maybe every few days. It goes away after about 10-20 minutes...about the time it takes to start realizing there's an issue and going to investigate.
When it's happening, I can ping IP addresses, but no name resolution works. I change my comp's DNS settings to Google and my name resolution works again.
I realized I had not run the IP updater in a while and my public IP was significantly different from what was on my OpenDNS page.
I downloaded the updater and everything looks right on my OpenDNS profile. I asked my wife to let me know if it happens again. If you don't hear from me, then running the IP updater prolly nailed it.
08-10-2016 09:07 PM
The Updater (or anything that provides similar functionality) is not something that should only be run occasionally, or when you think there are problems. It is something that needs to be running at all times, so that changes in your IP address are detected automatically and immediately, and automatically updated, resulting in no loss of service or protection.
08-11-2016 10:43 AM
@iguanac64
"I've been having the same problem as the original poster."
No, you don't, because you "do not have a Netgear router". The problem was specific to Netgear LPC only. It cannot happen with a different router.
"When it's happening, I can ping IP addresses, but no name resolution works."
In this case your problem is not related to the Updater either. It looks like a bug in the router's firmware.
08-12-2016 11:40 PM
Thanks, Matt...it wasn't intentional, just forgot to install it when I built my new computer a couple of years ago. Problem hasn't reoccurred in last three days since I ran the updated after reading your messages.
Rotblitz, possible...but my symptoms are exactly the same as the original poster's which is how I got to this thread. Same router last two+ years...only recently having the problem.
08-13-2016 09:08 AM
"Same router last two+ years...only recently having the problem."
Not changing anything is never a good argument for anything, especially not in IT. Rather to the contrary. Sometimes it is mandatory to change something to keep things going, because everything else around changes all the time.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide