Solved Be aware Forums.Freebsd.org is blocked when using OpenDNS as resolver DNS

R

rai.mohammed

Good morning all ;

I don't know if this section is the appropriate location for this topic, but I estimated the issue must be reported somewhere.

If you use OpenDNS as a resolver in your resolv.conf file, many websites will be blocked, and specially the case for Forums.Freebsd.org, with an error like below :


A01 - Forums-Freebsd-org blocked when using Opendns as resolver DNS - Page could not be loaded.png


So to overcome this problem, I cleared the cache and removed the cookies and the site data, to see what will happen :
A02 - Forums-Freebsd-org blocked when using Opendns as resolver DNS - Removing Cookies and sit...png

After that, I refreshed the page https://forums.freebsd.org, and I got the error from some web filtering Appliance [Cisco Umbrella] of https://block.opendns.com, throwing a message : "Sorry, forums.freebsd.org has been blocked by your network administrator" :-/, thanks god I am the only administrator of my home network :).
A03 - Forums-Freebsd-org blocked when using Opendns as resolver DNS - block-opendns-com.png


So to summarize and end up this post, the solution is to remove OpenDNS as a resolver from your resolv.conf file, and restarting [netif + routing] daemons, thank you I hope this will help someone newbie like me.
 
OpenDNS in and of itself does not filter anything (that is, if you use their 208.67.222.222/208.67.220.220 resolvers (which is "OpenDNS Home" I believe)).
Now, if you use one of their filter options, weird things may happen, and if Cisco Umbrella (within OpenDNS operating as "Family Shield", I think) decides that FreeBSD Forums is evil, then you won't be able to visit us (for reasons both unknown and not pursued).
So, use the first two resolvers, and nothing will be in your way.
 
DutchDaemon said:
OpenDNS in and of itself does not filter anything (that is, if you use their 208.67.222.222/208.67.220.220 resolvers (which is "OpenDNS Home" I believe)).
Now, if you use one of their filter options, weird things may happen, and if Cisco Umbrella (within OpenDNS operating as "Family Shield", I think) decides that FreeBSD Forums is evil, then you won't be able to visit us (for reasons both unknown and not pursued).
So, use the first two resolvers, and nothing will be in your way.
Click to expand...
I don't use any web filtering from OpenDNS, the blocking message came from OpenDNS web filtering solution Cisco Umbrella, from OpenDNS infrastructures.
I used OpenDNS resolvers [208.67.222.222, 208.67.220.220] in my resolv.conf file, that's all, so I switched to google IP @ and the issue was solved. For me FreeBSD Forums is awesome. 👍
 
I've been pointing my local network to OpenDNS for a long time and never had any issues. I do not use any filtering/Cisco Umbrella stuff, so I agree with SirDice that it's not an OpenDNS problem.
 
In my case, 208.67.222.222/208.67.220.220 live, together with about 10 other public resolvers, at the very end of my public-facing DNS infrastructure.
The Forums have never failed on me using those; it should have happened at least in 8-10% of my visits, since resolving is round-robin.
So, indeed, if you were using 208.67.222.222/208.67.220.220, the issue lies elsewhere.
Also note, it isn't a resolver error, the host clearly resolves; it's a filter error.
 
I use OpenDNS for more than 10 years and always worked. For what I remember only registered users (IP address) can customize filters, non registered user has no filter. If you register with a dynamic IP you should update the IP whenever it change to have filters enabled.
 
I saw similar error messages being thrown out by forums site a couple of hours ago. At the time, I chalked it up to network issues or forums server having a digital hiccup. I don't use OpenDNS.
 
I hate to add to an old thread but i was checking to make sure that we are supposed to add DNS servers to resolv.conf (i forgot if it is correct or not). I added my usual opendns to my resolv.conf but i searched Google to double-check that resolv.conf is correct for setting nameservers and this thread came up in the search results.

just to be clear: i have had this problem on Windows as well and it is not specific to any website. I suspect that my isp has something to do with it. I simply add around 5 dns servers so that i can switch whenever i have this problem. I have also had this problem with 8.8.8.8 Google dns. No worries, it is not you or openDNS filtering FreeBSD forums.
Anytime that you see this error, then switch the dns. I usually have to wait a few hours to a whole day before openDNS is working again...

edit: i also know that openDNS servers are often used by torrent programs (at least in the past, such as utorrent).
 
You must log in or register to reply here.
Back
Top