OpenDNS Home not working

Comments

4 comments

  • Avatar
    rotblitz

    You can check if your ISP redirects your DNS queries to their DNS servers.

    nslookup -type=txt which.opendns.com.  208.67.220.220

    - or -

    dig which.opendns.com txt @208.67.220.220

    1
    Comment actions Permalink
  • Avatar
    laurim

    Not sure how to interpret this info!  Any help is appreciated!

     

    Last login: Tue Apr  8 19:10:00 on console

    :~ Lauri$ nslookup -type=txt which.opendns.com.  208.67.220.220

    Server: 208.67.220.220

    Address: 208.67.220.220#53

     

    Non-authoritative answer:

    which.opendns.com text = "3.ash"

     

    Authoritative answers can be found from:

     

    :~ Lauri$ dig which.opendns.com txt @208.67.220.220

     

    ; <<>> DiG 9.8.3-P1 <<>> which.opendns.com txt @208.67.220.220

    ;; global options: +cmd

    ;; Got answer:

    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17377

    ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

     

    ;; QUESTION SECTION:

    ;which.opendns.com. IN TXT

     

    ;; ANSWER SECTION:

    which.opendns.com. 0 IN TXT "3.ash"

     

    ;; Query time: 19 msec

    ;; SERVER: 208.67.220.220#53(208.67.220.220)

    ;; WHEN: Wed Apr  9 06:52:05 2014

    ;; MSG SIZE  rcvd: 53

     

     

     

    0
    Comment actions Permalink
  • Avatar
    rotblitz

    Great, your ISP is not redirecting your DNS queries, and you would be using the OpenDNS WDC (ASH) location if you used OpenDNS.

    That said, you didn't configure the OpenDNS resolver addresses correctly (i.e. not all DNS server fields filled, or configured at the wrong place), or your settings simply do not take effect due to a bug, maybe in the firmware.  I assume you configured this on a router, as you said "Verizon network settings"?  Or you have configured different external resolver addresses on the end user device (Mac OSX 10.9.2).

    If there are more than two DNS server fields, fill them all.  There are additional addresses for this purpose: 208.67.222.220 and 208.67.220.222

    Some evidence could possibly be obtained from a variation of the previous command:

    nslookup -type=txt which.opendns.com.

    0
    Comment actions Permalink
  • Avatar
    laurim

    Success!  I went in and opened the broadband connection (ethernet/coax) settings and changed those as well and it worked like a charm.  Thank you!

    0
    Comment actions Permalink

Please sign in to leave a comment.