OpenDNS Forums
The official support and discussion site of OpenDNS
Support
K-12 Forums
Categories
- Administrative
- Adult site blocking
- DNS-O-Matic / dynamic IPs
- Domain blocking
- Domain Name System (DNS) troubles
- Mobile instructions
- OpenDNS services
- Proxies, accelerators, and more
- Router instructions
- Satellite
- Shortcuts
- Wishlists and feature requests
-
Feeds
Vanilla 1.1.4 is a product of Lussumo. More Information: Documentation, Community Support.
This discussion has been inactive for longer than 30 days, and is thus closed.
-
Indian ISP BSNL shares a common IP among all its user of EVDO connection. The common IP is
218.248.69.9
Someone has added this IP to the network and have blocked a large number of major sites including webmails like gmail, yahoo mail, hotmail etc.
I believe there should be someway to protect opendns from this kind of misuse.Thankful People: mrinal -
- CommentAuthorRed Prince
- CommentTimeJun 3rd 2009
You should open a support ticket, otherwise OpenDNS has no way of knowing about it.Thankful People: jax -
I opened a support ticket and no response from them after over a day. Still the issue is not resolved.
-
Incidentally, I started facing the same issue and came across this thread. I am also using BSNL in Bangalore and the same sites got blocked for me as well. Mine is a DataOne connection and my IP is dynamic but remains within 59.92.*.*
I have been using OpenDNS for sometime and this is the first time I am facing this issue. The problem (also) lies with corporates who use dynamic IPs thereby creating issues for home users. BSNL (in Bangalore) does provide static IPs for corporate connections. Its the BSNL home users here who cannot opt in for static IPs (not yet in Bangalore).
I had to reconfigure content filtering to get through this at my end. But enabling content filtering forced me to enable OpenDNS proxy which screwed my keywords usage on the address bar. This in turn changed the browsers default search behavior.
I can only hope that someone is seriously considering this issue. -
"the same sites got blocked for me as well"
So, as you apparently had no own OpenDNS network configured, you picked up the IP address and therefore settings of another OpenDNS user within this dynamic IP address range by chance. The other user had this IP address (and related settings) before, but didn't update his when changed.
"I have been using OpenDNS for sometime and this is the first time I am facing this issue."
The more people use OpenDNS, the more likely is the occurrance of these incidents.
"I had to reconfigure content filtering to get through this at my end."
So, in other words, you are using now your own OpenDNS network. Well done! This can prevent from using again someone else's settings.
"But enabling content filtering forced me to enable OpenDNS proxy which screwed my keywords usage on the address bar. This in turn changed the browsers default search behavior."
Disagreed. This is not really related to OpenDNS, but pure browser settings. So, what browser are you using, and what do you want to achieve with your "keywords usage on the address bar"? We may be able to provide you with the correct settings. -
I could not locate the support ticket, otherwise I would have commented there.
On second thoughts, it SEEMS that though content filtering rules are associated with an account in the dashboard, these rules, at some point, may get associated directly with an IP (maybe in some cache which is configured for faster rule access/mapping) and therefore this association isn't lost immediately if the account to IP association is lost. I may be forward guessing, but it is really annoying if my content filtering rules get modified accidentally with dynamic IP change which happens transparently through my ISP. -
"Disagreed. This is not really related to OpenDNS, but pure browser settings. "
Disagreed in return. Its not my browser's fault as it has been configured to use Google for keyword search. Now with the DNS proxy update, I am seeing the OpenDNS search results which I guess are powered by Yahoo. Hence the dissatisfaction.
"So, as you apparently had no own OpenDNS network configured, "
Disagreed again, as I have configured my home network in my account since the day I started using OpenDNS. It is quite probable that the previous owner of the IP may not have been so diligent which adds credibility to my assumption of rules to IP association.
Though I was able to revert my browser behavior by disabling the OpenDNS proxy after readjusting content filtering, this is more of a inconvenience if I had to do it every time I accidentally INHERIT someone else's configuration.
My recommendation would be to not allow rules to IP association in case of dynamic IPs. -
"I could not locate the support ticket"
Good to know that not everybody can access everybody's tickets.
No, tickets can be raised at http://www.opendns.com/support/contact/ and nobody beside OpenDNS staff can see them (and occasionally not even those...).
"maybe in some cache which is configured for faster rule access/mapping"
Yes, indeed, for this persistance two caches are responsible: the browser's cache and the local DNS cache. This can last for days and even weeks...
"it is really annoying if my content filtering rules get modified accidentally with dynamic IP change which happens transparently through my ISP."
This is only the case, if you don't keep your IP address updated in your dashboard. Download one of the Updaters, which do this automatically (and "transparently") for you.
"it has been configured to use Google for keyword search"
This works for me, with OpenDNS proxy enabled. It's really pure browser configuration. There is one difference: OpenDNS never returns NXDOMAIN for a non-existant domain, but a valid DNS result. This "confuses" some browsers, but you still can configure them not to rely on NXDOMAIN, before it goes to the default search. Let us know the browser you are using, and we may have advices about how it works for e.g. Google if searching from the address bar. (Did you realize that most browsers have now address bar and search field separated? What may have been the reason for this?)
"It is quite probable that the previous owner of the IP may not have been..."
As I wrote, you must keep your dashboard IP address updated to not run into this situation.
"to not allow rules to IP association in case of dynamic IPs"
What else should (or could) be the relationship between your network and your filtering/blocking rules? Does OpenDNS see something else beside your public IP address, which could be used to establish the relationship? -
@rotblitz
It would have been much productive if we worked together in understanding and debugging the issue rather than just trying to defend the effectiveness of the system. Bugs/issues are acceptable so long as support teams concentrate more on accountability of the issue rather than being defensive and challenging the knowledge of the customers.
I do not see this discussion being productive any more. It wasn't that a bad experience using the OpenDNS service than it was dealing with the support. I can only hope that others have a better experience with you. -
- CommentAuthormaintenance
- CommentTimeJun 16th 2009
Do you mean. like, if you had actually provided the name and version of the browser you are using? Or do you mean if you would keep your IP address updated? Which one of those most closely debugs the issue for you? -
@mrinal
You were not "dealing with the support", at least not here. Why did you think you were? This is primarily a user community forum, so you are dealing with users like yourself.
And @maintenance is right, YOU denied any collaboration, not providing browser details and not keeping your IP address updated - nothing! Don't search for assistance if you don't want and accept it!
1 to 11 of 11
This discussion has been inactive for longer than 30 days, and is thus closed.
