why are my websites blocked
"Every single thing of mine is blocked, and I cannot find the place to change that."
@mpriest76... Go ask you parents... we're not them.
With regards to the certificate error being seen, this is due to the SSL certificate checks done by browsers which is matching the expected domain to the block page and alerting you that they do not match. Please see https://support.opendns.com/entries/42398824-Adding-Exceptions-for-opendns-com-Certificates for more details. The browsers are correct to say there is a redirection, but in this case it's expected.
If you're experiencing unwanted filtering, run the following test and post the link to the results: https://support.opendns.com/entries/21841580 to check what your current settings are.
Yesterday, I spent several hours setting up Parental controls and keyword blocking from my Netgear WNR2000v4 Router. I connected and opened an account on OpenDNS. Everything seemed to be doing great except for two areas: 1) Several websites become "blocked" that should have been perfectly fine. For example, my kids would log into their schools, but when they clicked on a link to find out homework for classes they were attending, the router blocked access. The link to every class was blocked. I'm quite confident there was nothing in the keyword list that would be found on those pages!! 2) As good as the OpenDNS restrictions were to block inappropriate word searches on various pages and also block various less-than-kid-appropriate sites, it did not block questionable images in google (separate thread). I was desiring to implement forcesafesearch.google.com, but I could not figure out how to setup a CNAME on my network without installing a dedicated server. All-in-all, I was so disappointed with the experience that I reset the factory defaults on the router and now still do not have a solution for Parental Controls. I'm now searching to purchase software. Any recommendations anyone??
Why do you think this is an OpenDNS issue? Are you seeing messages that something is being blocked by OpenDNS? If the router is doing the blocking then you need to check the settings on the router itself, since OpenDNS is not doing the blocking.
It's hard to say what might be wrong with your configuration without knowing what you did to configure it.
OpenDNS does not block or filter keywords or word searches, nor does it block content on web pages, such as images. It is a DNS service, and the only blocking that it does is related to domain names that are being looked up.
There is no way to force Google safesearch on your entire network *without* setting up some sort of local DNS server. That is precisely what the directions (from Google, although OpenDNS does provide a link to them) say you need to do. Some routers have that functionality built into their firmware, often using DNSMasq, but I don't know if the firmware on your router supports it or not.
What exactly do you think OpenDNS offered that they didn't provide? If you want an OpenDNS related product to do Parental Controls then you need one of the routers that supports LPC, which leverages OpenDNS to provide some of it's functionality, but the OpenDNS portion of that is managed on a different page than the standard OpenDNS dashboard. One of the paid OpenDNS services could probably also do what you want, once it's properly set up.
As for asking on an OpenDNS forum about a product that you could use instead of OpenDNS, do you really expect to get advice sending you to a "competitor"? You'd be better off doing a search on the search engine of your choice, finding a non-vendor specific forum where such things are discussed, or contacting an IT professional who could help you.
There are a lot of very unhelpful comments in this thread.
The truth is that anyone who has a dynamically allocated public IP address, or even worse, has CGN imposed on them by the ISP, can find that sites ate being blocked 'by OpenDNS' and they, and no one they know, can do a thing about it.
All these comments about "ask your parents" and "ask your network administrator" are totally unhelpful.
The 'proper' answer is that OpenDNS should not allow any blocks to be applied on any address which is dynamically allocated by the ISP, or on any CGN gateway address.
How exactly are the comments of "ask your parents" or "ask your network administrator" unhelpful? Although some of them were snarky or condescending, that is exactly needs to happen if someone finds that domains are being blocked that they don't want to be blocked. The person who administrators the network or OpenDNS accounts needs to change settings somewhere, or in the unlikely case that they are using an IP address that is registered to someone else they need to get it properly registered to them.
If OpenDNS weren't to apply blocks on a dynamic address how exactly would OpenDNS's service work? The vast majority of people connecting to the internet are home user who receiving dynamic addresses from their ISP. Are you saying that OpenDNS shouldn't provide any service to them?
The only reason that someone who receives a dynamic address from their ISP would find domains being blocked by OpenDNS is if that person is already configured to use OpenDNS by sending their DNS traffic to OpenDNS. If they aren't doing that, every single address belonging to an ISP could be registered to someone's OpenDNS account but nothing would be blocked because they aren't sending *any* traffic whatsoever to OpenDNS, so OpenDNS wouldn't be blocking anything.
If someone who is already configured to use OpenDNS finds that they aren't using their own settings, but instead are using those of someone else it would be very obvious when they look at their dashboard and see that their account isn't associated with their IP and that for some reason they can't update it. In that case (as has been mentioned in other threads in this forum) all they need to do is open a support ticket with OpenDNS and they will resolve the situation very quickly.
That being said, I've used OpenDNS for years, and supported many other people who use OpenDNS, most of them using dynamic address, and have never personally run into a situation where an address was registered to someone else's account. If it were, it would be a simple matter to recognize the situation and get it resolved.
It's simple, OpenDNS does not impose any portion of their services on any internet user who is not already configured in some manner to use their services. They in no can force themselves upon anyone who does not want their service to be used and has not taken steps to configure their network to use the service.
"It's simple, OpenDNS does not impose any portion of their services on any internet user who is not already configured in some manner to use their services. They in no can force themselves upon anyone who does not want their service to be used and has not taken steps to configure their network to use the service."
This is true, insofar as I have configured my dns server/relay to use OpenDNS servers as the upstream servers. However, having done this, I find that I suffer random blocks on random sites which I have not configured ... and I am adminstrator for my own house - there is no one else here to perform the role.
However, my problem arises because my site is only one of many sharing the same public IP, ever since my ISP imposed CGN last December.
Are you saying that OpenDNS copes with the fact that, under dynamic address allocation, a site's public IP will change every time the router/modem is rebooted (and, sometimes, more often)?
When I was in UK, I was accustomed to having a unique, static, IP. Since moving to PhilippinesI have had to cope with ever-changing public IPs (especially since we suffer an average of two power cuts a day). However, since December I am back to always having the same public IP - the problem being that several hundreds (or thousands?) of other sites are connecting with the same public IP.
There's a huge difference between a dynamic IP address (a pool of IPs is distributed to active users) and an IP address which is shared by many users at the same time (NAT IP). Please provide your IP address in a new support case to email@example.com and reply here once done. If your IP is indeed shared by hundreds of users at the same time, we do exclude such IPs from being filtered because they are shared by many concurrent users. If your IP changes often, consider using the Dynamic IP Updater client to keep your own up to date so filtering applies where expected: https://support.opendns.com/entries/23282614.
Okay, so you're saying that, provided all OpenDNS users use a 'dynamic IP updater client' (similar to DDNS?), then filters will not be incorrectly applied to the wrong user? That makes sense.
However, in my case this doesn't help - I've been on the same public IP for the last month - along with many other local customers of this ISP - through a CGN (Carrier Grade NAT) implementation. On of the users in this NAT group applies an OpenDNS filter, and everyone gets filtered!
I've reported the IP to support.
In the meanwhile I will try to get the ISP's customer service to understand the problem, and see whether there's a possibility of getting off CGN.
Assuming everyone on a dynamic IP used the updater client, there would be very few conflicts (some would still register as static of course). It wouldn't help much with NAT setups since everyone would have the same IP on the NAT and only one person's settings could apply. I've also followed up to your support request.
All of this is fine if one has a clue what you are talking about. I just punch the keys and do the functions. I never loaded opendns on my single laptop, yet here it is. How does one open a ticket with opendns
See the tab "Submit a request" on top of this page?
hello i cant open xnxx
pleas help me
I have no idea what xnxx is, let alone it's domain name, or even better, it's website address.
Without knowing more all I can say is that the reason you can't get there is because your OpenDNS settings are blocking one or more of the domains associated with xnxx.
You should look at what you are filtering, and either change the settings or whitelist the impacted domains. To confirm what domain might be blocked you should look in your logs and stats.
Post is closed for comments.