Adult content being Blocked :-)

[y2ken]

I have Windows 10 Pro and run a virtual Linux Mint 'guest' OS with VirtualBox.

Adult content is being blocked even though content filtering is turned off. Nothing gets blocked on my main Win 10 OS just the virtual Linux Mint which should be sharing the same network configuration as the 'host' Win 10 OS. I've tried enabling/disabling but it didn't help. If I use my ISP's DNS or Google DNS I don't have this issue.

[mattwilson9090]

You say the Linux OS "should be" sharing the same network configuration as the host Win 10 box. How should it be sharing that? Have you confirmed that it actually is using the same network settings (other than IP address)?

Of the top of my head, aside from comparing those network configuration settigns, I'd suggest making sure that your IP address is properly registered on your OpenDNS network, and that you are not sending any DNS traffic via IPv6. For testing purposes you could disable IPv6 on an individual PC, but ultimately you should be disabling IPv6 on the router itself.

[rotblitz]

If you're still having problems after following the advices from mattwilson9090, post the complete plain text output of the following diagnostic commands here, two times, taken from your Linux VM and from your Windows 10:

   nslookup -type=txt debug.opendns.com.

   nslookup www.exampleadultsite.com.

[y2ken]

I am not a networking expert but I say "should be" sharing the same network configuration because both OS's are running on the same PC which has only one network card which connects to my one router. So they are for sure using the same network but maybe not the same network 'configuration'. ? There are only a few choices in the VirtualBox networking section. [screen shot attached] The Linux 'guest' network adapter is "Attached" using "NAT". The other networking choices are to 'attach' via, NAT Network, Bridged Adapter, Internal Network, Host Only Adapter, or Generic driver.

My OpenDNS dashboard shows that my IP address is the same as the host OS. I also noticed that my network shows as "inactive" [see screen shot]. I clicked on the link for OpenDNS to send me a verification email, but when I click on the verification link in the email it says "your IP address does not match the one that you are trying to verify". WTF ?

Capture2.JPG
Capture.JPG
Capture1.JPG

[rotblitz]

"My OpenDNS dashboard shows that my IP address is the same as the host OS."

Hardly. Your host and VM have RFC-1918 IP addresses (for use in private networks) whereas OpenDNS sees your public IP address only.

"I also noticed that my network shows as "inactive""

This indicates that your current public IP address is either registered with another user's OpenDNS network, or that this IP address cannot be registered with OpenDNS at all, because it may be from a range of shared IP addresses.

Instead of having posted these rather useless screen shots, you better had posted the outputs of the diagnostic commands.

No matter, this most likely cannot be solved by you or us users, unless maybe by obtaining another IP address.  You'll have to open a support ticket with OpenDNS.

[y2ken]

It's not worth all this trouble. Everything works perfectly with Google DNS so I'll just go with that.

[rotblitz]

Fine, if you like that they spy you for even more "targeted advertising" and whatever stuff, go for it!  And yes, that works perfectly!
http://www.pcworld.com/article/183671/Google_Public_DNS_and_Your_Privacy.html

[y2ken]

I got it working properly without your help or criticism. Thanks for nothing.

[mattwilson9090]

How did you get OpenDNS working for you? Or does that mean you just ignored OpenDNS and went to Google instead?

[eleung12]

Hi y2ken,

Sorry to hear you are having issues with content filtering. If you are still having issues while running OpenDNS, please submit a ticket to our staff so that we can discuss your account details with you. If you could please include the diagnostic information for Linux in your virtual box and send us the results in a text file, that would help us investigate the issue.

Cheers!