Support

K-12 Forums

Talk with other K-12 network administrators in your state.

Or see all states.

Categories

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.

Domain blocking: OpenDNS and McAfee SiteAdvisor

Bottom of Page

1 to 31 of 31

  1.  
  1.  permalink
    I use McAfee SiteAdvisor as a Firefox add-on and like it but since I set up OpenDNS it is no longer working. I tried putting the SiteAdvisor domain in my whitelist but that did not help. Is it not possible to use the two together?
    • CommentAuthorpencoyd
    • CommentTimeMar 10th 2008
     permalink
    Could you be more specific about what's not working?
    • CommentAuthorwubba
    • CommentTimeMar 10th 2008
     permalink
    @pencoyd-
    Below are 2 comments from a Linkscanner thread I had posted that might be more specific about eremita2511's experience... and if not, it is something I am experiencing still ;-)


    "This might explain why McAfee's SiteAdvisor, (Firefox 2.0.0.12 browser plugin 26.5), is doing the same thing. Although the regular safe surfing button works for individual web pages, it no longer color code highlights Google search results as it has in the past. This issue began approximately a week ago for me, and I assumed it was a McAfee problem. Could it actually be a change in OpenDNS that is causing the problem? Anyone else having a similar issue? Thanks.


    @mnordhoff
    I have been following the thread that you pointed out for awhile, (been using OpenDNS since summer 2007), and the problem with SiteAdvisor and Google searches began just about a week ago, (all had been working well up to that point). I am assuming that the current problem is a separate issue from the one you've pointed out. Thanks."
    • CommentAuthortonor
    • CommentTimeMar 10th 2008 edited
     permalink
    I too have noticed the change in behaviour regarding SiteAdvisor and Google search results pages. The colour code markers are no longer visible.

    I do use the Firefox browser, and have the Adblock Plus plugin installed. I did think there was an update to the subscriptions that may have blocked the colour code images, but disabling the subscriptions or Adblock Plus completely doesn't change the situation regarding the coloured markers.
    • CommentAuthorpencoyd
    • CommentTimeMar 10th 2008
     permalink
    I'm downloading SiteAdvisor to learn more.
    • CommentAuthorwubba
    • CommentTimeMar 10th 2008 edited
     permalink
    addendum:
    I momentarily switched to my ISP's dns servers, and SiteAdvisor started working properly for Google searches again. When I switched back to OpenDNS, the problem occurred again. I'd give up SiteAdvisor before giving up OpenDNS, however ;-).

    It would be nice if they played well together though...
  7.  permalink
    I really don't know what is my trick...

    http://img369.imageshack.us/my.php?image=imagemji1.jpg
    http://img369.imageshack.us/my.php?image=imagem2dd7.jpg

    Maybe is because sometimes I switch from a DNS server to another to make tests and the address stay in cache, but I think no...

    I am downloading siteadvisor in another computer other than mine to take a look too. This little gadget is a good one to recommend.
  8.  permalink
    UPDATE: I just installed McAfee SiteAdvisor on another machine. Is a laptop that a friend let to me format this weekend and the first thing I did on it after install the network drivers was set up OpenDNS, so I think no issues with caches. Worked fine, again, a picture:

    http://img368.imageshack.us/my.php?image=opendnszk9.jpg
  9.  permalink
    I am the originator of this thread. Here is more specific information.

    SiteAdvisor no longer tags or colors search results although it will permit me to check the status of a page once it is loaded. I tried putting "www.siteadvisor.com" in my OpenDNS white list but that didn't seem to help.

    I have double checked that it is OpenDNS as the conflict by going back to my original set-up and SiteAdvisor then color codes and tags the search results.

    I am using Firefox on a Win XP Home fully patched and updated. I also use AdBlock Plus and NoScript

    Is there any other information that I can provide that might prove helpful?
    Thankful People: srday
    • CommentAuthorsrday
    • CommentTimeMar 11th 2008
     permalink
    This is DEFINITELY a (recent) problem on TWO (geographically separate) networks I manage. (One is in PA, and the other is in CO.) Both network began having problems in the last week, despite the fact that I've used Open DNS on them for considerably longer.

    I believe OpenDNS's "solution" to the Google "problem" prevents SiteAdvisor's "safety ratings" from appearing in (Google) search results. It also causes an unacceptably long delay in loading Google search results.

    I like OpenDNS, but I'm NOT happy with their "solution" to this "problem." IS THERE ANY WAY TO TURN OFF THE GOOGLE INTERCEPT? (Please don't tell me to turn off the Shortcuts I DON'T use...)
  11.  permalink
    @eremita2511

    I am at home now, and did some more tests, with more time.

    First, I use wireshark to sniff what is happening, take a look:

    http://img389.imageshack.us/my.php?image=wiresharkkd6.jpg

    So the only thing with DNS is done by siteadvisor is query a simple host, and it resolves fine.

    But then I do test a search on google again and bingo! It doesn't work!!!
    So I became amazed, how few hours ago on that laptop worked...
    Wireshark give me the answer too. When you ask for www.google.com, OpenDNS is well know to redirect to google.navigation.opendns.com. As opendns.com is not same as google.com I *guess* this not trigger the SiteAdvisor plugin.
    But how that laptop worked before? So I check the screenshoot again (I was in doubt of myself!!!) and noticed that was google.com.br and not just google.com. I did the test again, this time with google.com.br and worked! So I try yahoo.com and works too... But use google.com and don't work, because with OpenDNS google.com isn't google.com, is google.navigation.opendns.com.

    So, my verdict:

    SiteAdvisor DOES work with OpenDNS

    Is just another side effect of that Google issue that is subject of another threads.

    Try with google.com.br or yahoo.com and see if works for you too!
    • CommentAuthortonor
    • CommentTimeMar 11th 2008 edited
     permalink
    I can confirm that with google.co.uk, the SiteAdvisor safety ratings appear in the search result listings. That's fine, but the Firefox search box for Google automatically goes to google.com, which is where the problem appears to be.
    • CommentAuthorsrday
    • CommentTimeMar 11th 2008
     permalink
    Unfortunately, SiteAdvisor safety ratings do NOT work for me when using google.co.uk. The site also suffers from the same LONG (intolerable) delay as its U.S. cousin does.

    They do, however, function correctly on Yahoo!
  14.  permalink
    After testing, I have found so far that SiteAdvisor highlights and tags search listings with

    yahoo.com
    search.msn.com
    google.com.br
    google.co.uk
    google.ee
    google.com.au
    google.ca
    google.com.cu
    google.gy

    and every other one I tried except my default google.com either evoked by Firefox or typed in manually.

    So if it is a google.com issue, I guess I need to find out how to change the default Firefox Google search to google.ca until some other fix is found.

    Thank you to all who have helped to narrow this down (at least for me). Strange how google.co.uk highlights for me (and quickly) but not for srday. I am in Texas.
    • CommentAuthortonor
    • CommentTimeMar 11th 2008
     permalink
    » "So if it is a google.com issue, I guess I need to find out how to change the default Firefox Google search to google.ca until some other fix is found."

    Close Firefox, go to program files\mozilla firefox\searchplugins, open google.xml in a text editor, look for references to google.com and change to google.ca. Save the file and restart Firefox, test the search bar and you should find the results come from google.ca.
  16.  permalink
    tonor wrote:

    "Close Firefox, go to program files\mozilla firefox\searchplugins, open google.xml in a text editor, look for references to google.com and change to google.ca. Save the file and restart Firefox, test the search bar and you should find the results come from google.ca."

    I was pretty sure with Firefox it wouldn't be difficult to change and it was not. I saved the original xml file for after the eventual fix and did a universal change of google.com to google.ca. It seems to be working well so far.

    Thank you.
  17.  permalink
    Blessed be the XML
    • CommentAuthorsrday
    • CommentTimeMar 12th 2008
     permalink
    Based on suggestions in other threads, I contacted OpenDNS support to request that they disable Shortcuts on my account. (Google redirection is supposedly tied to the use of Shortcuts.)

    The good news is that the Support team resolved the problem for me within an hour. Google requests from both networks I manage are no longer redirected through “google.navigation.opendns.com.” (Google) searches now run as quickly as ever and, once again, include McAfee SiteAdvisor “safety ratings.” According to the Support team’s response to my inquiry, they “altered a setting in your account which should resolve this matter until we come up with a more permanent solution system-wide.”

    The bad news is that both “typo correction” and “shortcuts” had to be disabled to get here. Unfortunately, many OpenDNS “features” (e.g., Content Filtering and Adult Site Blocking) rely on these and are, therefore, also disabled. According to the Support team, only Phishing Protection remains available. My Dashboard, however, indicates Domain Whitelisting and (individual) Domain Blocking are still functional.

    Additional bad news came in response to my inquiry about when the “more permanent solution system-wide” might be available for those of us who'd like to take advantage of Content Filtering and Adult Site Blocking without the Google performance hit and loss of SiteAdvisor “safety ratings.” Their response now states “our business model is based upon using this feature and you cant have one without the other.” They went on to say “we cannot make this change each time your IP updates. You will need to use software to keep it updated in your account. Keep in mind that this is not something we normally do for users, since as you have seen first-hand, that it disables all of our other services.”

    I’m not sure how this equates to a “more permanent solution system-wide…?” It’s also worth noting that my Idea Bank suggestion, that users be allowed to opt-out of the Google redirect, has gone nowhere (i.e., has not been approved for a vote of the users) since I submitted it a couple of days ago.
    Thankful People: mnordhoff
    • CommentAuthorpencoyd
    • CommentTimeMar 13th 2008
     permalink
    @srday - The SiteAdvisor conflict is temporary, and we're working to resolve it. It's a side effect, not the point. The reference to a full solution is regarding the SiteAdvisor issue.

    The valuable features you're interested in require typo correction and shortcuts to be enabled.

    OpenDNS uses IP addresses to keep your custom preferences (guide branding, filtering preferences, stats, etc.) aligned with your account. OpenDNS has __always__ required that our customers with dynamic IPs keep the IP updated in the OpenDNS Dashboard. The easiest way to do that is to run software, as it says here: http://www.opendns.com/support/dynamic_ip/

    It doesn't matter WHAT the preferences are -- you have to keep your IP updated if it's dynamic. That's not new and it's a technical obstacle which we'd like to remove, but don't have anything immediate.

    John
    • CommentAuthorsrday
    • CommentTimeMar 13th 2008
     permalink
    That’s good news. Thanks for the clarification. FWIW, my concern was not with the need to update the dynamic addresses my networks use. (Configuring them to automatically do so makes sense, IMO, and was never an issue. I only included that requirement for others who might be interested in pursuing the workaround your folks implemented for me.) Nor do I have any problem enabling/using Typo Correction or Shortcuts, assuming they do NOT kill Google performance and SiteAdvisor “safety ratings.”

    What I, apparently, didn’t convey properly was that I took your Support folks’ response to indicate users would have to CHOOSE

    Option 1: OpenDNS “features” like Content Filtering and Adult Site Blocking
    OR
    Option 2: Decent Google performance and SiteAdvisor “safety ratings”

    As I understand your latest post, users will NOT have to make this choice. Instead, your staff is working on a solution that will allow us to enjoy BOTH options above, assuming we're willing to enable Typo Correction and Shortcuts. Please let me know if I’ve misinterpreted...
    • CommentAuthorpencoyd
    • CommentTimeMar 14th 2008
     permalink
    The SiteAdvisor conflict with OpenDNS is what causes the Google results to be slow. That's what we're working on. These are not separate issues.
    Thankful People: wubba
    • CommentAuthorpencoyd
    • CommentTimeMar 14th 2008
     permalink
    This has been fixed.
    Thankful People: wubba, srday, eremita2511
    • CommentAuthormnordhoff
    • CommentTimeMar 14th 2008
     permalink
    Out of curiosity, what was wrong?
    • CommentAuthorwubba
    • CommentTimeMar 14th 2008
     permalink
    I can confirm that SiteAdvisor is now working here with Google searches. Thanks!
  25.  permalink
    My Google searches are once again tagged and color coded by SiteAdvisor. Thank you!
    • CommentAuthorsrday
    • CommentTimeMar 14th 2008
     permalink
    Working here as well. Thank you!
  27.  permalink
    Looks that OpenDNS does now redirect Google to the "official" IPs

    #############################################################################
    C:\>nslookup www.google.com resolver1.opendns.com
    Servidor: resolver1.opendns.com
    Address: 208.67.222.222

    Não é resposta de autorização:
    Nome = www.l.google.com
    Addresses: 74.125.47.147, 74.125.47.104, 74.125.47.99, 74.125.47.103
    Aliases: www.google.com
    #############################################################################

    Although my regular DNS server disagree about the address...

    #############################################################################
    C:\>nslookup www.google.com
    Servidor: xxxxx.local
    Address: 192.168.1.1

    Não é resposta de autorização:
    Nome = www.l.google.com
    Addresses: 64.233.169.103, 64.233.169.147, 64.233.169.104, 64.233.169.99
    Aliases: www.google.com
    #############################################################################

    Maybe Google use round robing or something like...
    Anyway, both answers looks from Google anyway:

    #############################################################################
    C:\>tracert 64.233.169.103

    Rastreando a rota para yo-in-f103.google.com [64.233.169.103]
    com no máximo 30 saltos:

    1 <1 ms <1 ms <1 ms someserver.local [192.168.3.5]
    2 1 ms <1 ms 1 ms ????.customer.tdatabrasil.net.br [200.148.???.???]
    3 8 ms 9 ms 8 ms ????.customer.tdatabrasil.net.br [200.159.???.???]
    4 * * * Esgotado o tempo limite do pedido.
    5 10 ms 10 ms 10 ms 201-0-2-89.dsl.telesp.net.br [201.0.2.89]
    6 10 ms 10 ms 10 ms 201-63-253-114.customer.tdatabrasil.net.br [201.63.253.114]
    7 12 ms 13 ms 12 ms ge4-1-0-0-grtsaosi2.red.telefonica-wholesale.net.10.16.84.in-addr.arpa [84.16.10.45]
    8 119 ms 119 ms 118 ms so5-2-0-0-grtmiabr4.red.telefonica-wholesale.net [213.140.36.65]
    9 165 ms 149 ms 149 ms so3-2-0-0-grtwaseq2.red.telefonica-wholesale.net [213.140.43.125]
    10 * * * Esgotado o tempo limite do pedido.
    11 147 ms 150 ms 148 ms 209.85.130.18
    12 150 ms 150 ms 147 ms 64.233.175.171
    13 154 ms 149 ms 156 ms 216.239.49.145
    14 147 ms 150 ms 147 ms yo-in-f103.google.com [64.233.169.103]

    Rastreamento concluído.

    C:\>tracert 74.125.47.147

    Rastreando a rota para yw-in-f147.google.com [74.125.47.147]
    com no máximo 30 saltos:

    1 <1 ms <1 ms <1 ms someserver.local [192.168.3.5]
    2 <1 ms <1 ms <1 ms ????.tdatabrasil.net.br [200.148.???.???]
    3 8 ms 8 ms 9 ms ????.customer.tdatabrasil.net.br [200.159.???.???]
    4 * * * Esgotado o tempo limite do pedido.
    5 10 ms 9 ms 9 ms 201-0-2-81.dsl.telesp.net.br [201.0.2.81]
    6 10 ms 10 ms 10 ms 201-63-253-118.customer.tdatabrasil.net.br [201.63.253.118]
    7 12 ms 13 ms 11 ms ge4-1-0-0-grtsaosi2.red.telefonica-wholesale.net.10.16.84.in-addr.arpa [84.16.10.45]
    8 118 ms 118 ms 118 ms so5-2-0-0-grtmiabr4.red.telefonica-wholesale.net [213.140.36.65]
    9 149 ms 147 ms 149 ms so3-2-0-0-grtwaseq2.red.telefonica-wholesale.net [213.140.43.125]
    10 * * * Esgotado o tempo limite do pedido.
    11 147 ms 150 ms 156 ms 209.85.130.18
    12 162 ms 165 ms 161 ms 216.239.48.69
    13 160 ms 152 ms 146 ms 209.85.254.241
    14 154 ms 161 ms 147 ms 209.85.253.157
    15 150 ms 147 ms 147 ms yw-in-f147.google.com [74.125.47.147]

    Rastreamento concluído.

    C:\>
    #############################################################################

    So my guess is that OpenDNS doesn't more have that issue with Google

    Thanks folks
    • CommentAuthorsteveshank
    • CommentTimeMar 17th 2008
     permalink
    My problem with the two of them is that whenever I start firefox I get the following message:

    -----------
    Security Error: Domain Name Mismatch
    You have attempted to establish a connection with "dss1.siteadvisor.com". However, the security certificate presented belongs to "www.opendns.com" ...

    Followed by another one about dss2.siteadvisor.com.

    I really like using both, but don't like multiple error messages on every startup.
    • CommentAuthorpencoyd
    • CommentTimeMar 17th 2008
     permalink
    http://www.opendns.com/support/article/153

    What version of Firefox are you using?

    Also, we've traded notes with SiteAdvisor, and they are releasing an update on their end this week. We already put in place a fix for the issues people were seeing, but their work should completely eradicate the issue from ever happening again.
    Thankful People: wubba
  30.  permalink
    Interestingly, this happened to me just now when I opened Firefox on the Dell desktop. It complained about the security certificate but it happened only once. And when I closed down Firefox and restarted it, I did not get a complaint. Perhaps it held the OK in some kind of memory??

    But I have noticed that recently when I start Firefox there is a long lag before the home page loads which in my case is a local file. I am wondering if it has anything to do with the SiteAdvisor fix or is just a coincidence. Once it seemed to freeze and I finally Ctl-Alt-Del to close down and start over but perhaps I did not wait long enough.
    • CommentAuthormasa
    • CommentTimeMar 18th 2008 edited
     permalink
    eremita2511 & steveshank:

    It's siteadvisor problem. Apparently the site is going up and down and all around (could be because of all the pings it makes).

    Ex. 4 minutes ago, I couldn't connect to the site. Now I can.

    The cause:

    The problem is dss1.siteadvisor.com is up and down all the time. When it's down, OpenDNS needs to tell you that dss1.siteadvisor.com is FAIL-ing and shows you the OpenDNS FAIL page. Of course, opendns.com isn't dss1.siteadvisor.com and so, since you tried to connect to dss1.siteadvisor.com but got opendns.com you get this message:

    Security Error: Domain Name Mismatch
    You have attempted to establish a connection with "dss1.siteadvisor.com". However, the security certificate....

    The reason:

    So people don't use a SSL cert maliciously, by using another site's certificate. If there was no warning, I could set up a phish page with PayPal's cert (or another cert from another site easier to hack) and it would have https:// thus, fooling a lot more people (because everyone says you are safe with https:// NO MATTER WHAT THE URL IS [wrong])

    In this case, you should be fine. But since siteadvisor can't connect it might not work. The bad thing is that siteadvisor might possibly send your info over...http...if it fails.

    The fix:

    According to McAfee, the easiest way to solve this is by contacting them: http://www.siteadvisor.com/feedback.html

    More complex, you can hack around and use http instead of https if you want to dive into code. You won't see those messages about mismatching, but your queries will not be encrypted.
    Thankful People: eremita2511

1 to 31 of 31

  1.  

This discussion has been inactive for longer than 30 days, and is thus closed.