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.
-
Hi
I am seeing access to ajax.googleapis.com being blocked as a Phising site, I believe that categroiseing this site as Phishing will cause major issues for many users as its the CDN address for Google's API collections such as jQuery and MooTools
Anyone else seeing this issue or is it just me?
Al -
I have had to disable Phising Protection in the Security section as Whitelisting the domain still blocked access to it, I guess this is due to the 3 minute delay in updating the Witelist?
-
- CommentAuthordjtarazona
- CommentTimeJan 4th 2012
Yup, I'm seeing this too. OpenDNS is blocking as phishing. -
Yep, I am also seeing this :(
-
This was driving me insane! I can confirm this is happening.
-
Yep, I am also seeing this :(
90% sites is broken :( -
Same problem here ... :(
You need to fix this asap..! -
we are also seeing this
-
Same here
-
This is really annoying. If this doesn't get fixed quickly OpenDNS is going to lose a lot of users.
-
I have to admit this is the first time I have found OpenDNS to be a problem, but it is a rather big one for us. Never considered disabling OpenDNS until today...
Especially worrying as our site uses Google CDN and if our users IT teams use OpenDNS our sites won't work at all.
Can OpenDNS "ring fence" domains that can't be affected by mistaken or malicious updates to categories (I'm assuming this is the problem here)? -
-
CommentAuthorDaniel Gifford
- CommentTimeJan 4th 2012 edited
AdministratorHello,
I have de-listed the domain on our servers and forwarded this to our Phishtank team to investigate why it was listed and take the appropriate measures to prevent this from happening in the future. You may need to clear your cache and flush your resolver. We apologize for any inconvenience.
Daniel Gifford
OpenDNS -
-
Thanks for sorting this out so quickly.
A cache flush was required on OS X to get it working again.
dscacheutil -flushcache
1 to 13 of 13
This discussion has been inactive for longer than 30 days, and is thus closed.