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.

Administrative: What Happened: Unresolved domains in Firefox no longer go to google but trigger an OpenDNS search?

Bottom of Page

1 to 5 of 5

  1.  
    • CommentAuthorwdr1
    • CommentTimeJul 3rd 2009
     permalink
    I started using OpenDNS maybe six months ago. For a long time, if I entered a domain that didn't resolve into Firefox (e.g., "docs") it effectively conducted an "I'm feeling lucky" search on Google. E.g., I'd be redirected the first result, which in this case is 'docs.google.com'.

    In the last few weeks, that behavior has changed. For terms that shouldn't resolve to an IP, they seem to & instead I'm presented with an OpenDNS-branded set of Google results.

    I logged in to my account to see how I disable it once again, but can't find it.

    I'm somewhat annoyed as it's a fairly disruptive change to me. Can anyone point me in the right direction?
  2.  permalink
    Dashboard > settings > advanced settings > domain typo correction

    Or see how to tweak the browser back to the old FF behavior (before address bar and search box were separated)
    http://forums.opendns.com/comments.php?DiscussionID=3278#Item_5
    • CommentAuthorrotblitz
    • CommentTimeJul 3rd 2009
     permalink
    "In the last few weeks, that behavior has changed."
    Did you upgrade FF to a later version? Or did you browser reconfigurations of any kind, maybe unintended?

    "I'm presented with an OpenDNS-branded set of Google results."
    Nope, this is Yahoo, not Google, but don't worry...

    Btw, read the thread recommended by @maintenance until the end, or select another:
    http://forums.opendns.com/search.php?PostBackAction=Search&Keywords=feeling+lucky&Type=Comments&btnSubmit=Search
    Depending on your version of FF the solution may slightly vary.
    • CommentAuthorwdr1
    • CommentTimeJul 4th 2009
     permalink
    Let me take firefox out of the equation.

    If I try to lookup a domain that doesn't exist, here's what I get on another machine:

    % nslookup idontexistfdafdafdsafdsa
    Server: 10.0.80.11
    Address: 10.0.80.11#53

    ** server can't find idontexistfdafdafdsafdsa: NXDOMAIN

    If I do it on a machine that uses OpenDNS, I get:

    >nslookup idontexistfdafdafdsafdsa
    Server: sekret
    Address: 192.168.1.1

    Non-authoritative answer:
    Name: idontexistfdafdafdsafdsa.socal.rr.com
    Address: 208.67.219.132

    208.67.219.132 is an opendns server. I don't want it to that. I want it to say that IP doesn't exist.

    Put FF back into the equation, saying that IP doesn't exist will then trigger the appropriate behavior.
  5.  permalink
    Sorry, but we've tried to explain. You'll need to adjust the browser.
    OpenDNS does not return NXDOMAIN. You get hit-nxdomain.opendns.com (the Guide). This is how OpenDNS service can be had for free (sponsored search results). This is not going to change.

1 to 5 of 5

  1.  

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