Something I must be missing about dynamic IP support in OpenDNS.

Don't data and services get co-mingled (or just plain mishandled) when dynamic IPs change (i.e., when OpenDNS receives DNS queries from an IP that it thinks belongs to someone else)?

For example, if someone else is blocking domains and using an IP address that I am subsequently assigned by my ISP, then don't I get blocked too? At least until the dynamic IP updates occur by either me or the other customer? What about the case when the other customer doesn't do these updates at all . . . maybe doesn't have the technical ability to do it? What about the case for OpenDNS users who don't have accounts at all?

Am I missing something here? I hope I am.

This seems to me like a deal breaker for dynamic IP use of the entire OpenDNS system. I don't ever want OpenDNS to facilitate others tracking my DNS use (intentionally or not), or to accidentally impose services on me.

You could mitigate this if you . . .
a) allowed IP addresses to be declared dynamic (or better, deal with all of them as dynamic unless proven static).
b) for such addresses, disable all OpenDNS services if the IP hasn't been updated within some short period of time.
c) quarantine all DNS history for those IPs, releasing it for storage (and display) only if the subsequent IP update matches the previous update (i.e., the same user updated the IP). Otherwise, purge it.

A major issue here is if user A creates an account with a dynamic IP and never updates it. user B comes a long (no account necessary) and starts using OpenDNS. When they get the first user's IP, the problem happens and, worse, user B never knew this was a possibility.

Troubling.

Yeah, I see that people declare the IP dynamic, but by default your service assumes they are not. I'm surprised that these so-called "edge" cases aren't clearly spelled out.

The only reason this may not be a major issue is due to penetration . . .

Thanks for your response -- I'm not convinced.

Just wondering how opendns services behave in following 2 scenarios (dynamic IP)

1) user A uses opendns servers as well as other services of opendns and he doesn't update or use his netwrok (ex: dsl connection) for some time and then user B from same ISP gets same dynamic IP and happen to use only opendns servers not any other stuff including dns-o-matic.

Is user B is treated as user A and his filter setting etc. are used for user B?

2) Only change from 1) is that user B also uses all services and updates his dynamic IP with dns-o-matic

Now 2 accounts on opendns have same IP, how are the stats and other stuff is treated?

I could see I have some site accesses from my network at the times I am not around at home and blocked sites which are not supposed to be blocked according to my filter settings.

well, i got the same issues two times so far ! update.microsoft.com was blocked and i had to get a new public ip by restarting router !

You mention everywhere "put this ip in your dns settings" . many people wont be bother to update their ip or blacklist some site. So people who are having less knowledge about OpenDNS is suffering !

You guys are saying millions of people are using this service. the more people use this service, the more problem we face ! Either you give your service only to Static IP's or stop that blacklist service !

@appus
You are right, this is a well known problem, and reported in many threads here in the forum already. I am sure that OpenDNS are already looking for a solution to overcome this. My proposal is the same as several other users have expressed: the current "owner" of a dynamic IP address should be the winner over a lazy user, who did not update his/her IP address.

That way any user behind a filtered network (e.g. in schools) could take over the IP and unblock everything.

I never had problems with the way it currently works. Dynamic IP's are released after some hours.

Hello guys.. I am living in a hostel. My network of admin has blocked port of my game. (Port : 7000) Is there any way escape the blocking or what else?

I really need it :)