OPENDNS not working on my BOSE sound touch speakers and other computers in my household

Comments

5 comments

  • Avatar
    mattwilson9090

    Generic instructions for configuring your network, or devices on your network, to use OpenDNS begin on the OpenDNS Homepage. For some particular router models there are even specific guides since some router models require additional steps to work properly. Rather than retyping information that OpenDNS has already published I'll direct you there.

    Of course if you have specific problems or questions I (and other users of this forum) will be happy to address those.

    It's possibly that something in the router prevents you from using other DNS services, or that your ISP is doing something to block or redirect DNS queries that go anywhere but to their servers.

    0
    Comment actions Permalink
  • Avatar
    rotblitz

    @Llyrio

    It seems that you have the OpenDNS resolver addresses configured on the LAN/DHCP side, and this impacts or breaks local name resolution with the effect that you cannot connect to your internal devices by network name any longer, because OpenDNS cannot resolve your internal network names.

    See if you can configure OpenDNS on the WAN side of the router.  If this is not possible, try to access your devices by their internal IP address instead of by their network names.

    "I installed OPEnDNS"

    You cannot install OpenDNS, because OpenDNS is not software but an online service.  You can just configure it.

    "how install the whole software and DNS update again"

    There is no "whole software" but the Updater only.  And this has nothing to do with your problems and does not need any further action at this time.  Just leave it and use it.

    If you need further assistance, post a screen shot of the router page where you have OpenDNS configured.  Also copy & paste the complete plain text outputs of the following diagnostic commands to here:

    nslookup -type=txt debug.opendns.com.
    netsh interface ipv4 show config

     

    0
    Comment actions Permalink
  • Avatar
    Llyrio

    Please see the attached screen grab.

    When I said installed, I meant configured.

    diagnostics:

     

    Last login: Thu Mar  2 07:54:42 on console

    Restored session: Wed  1 Mar 2017 14:27:08 GMT

    Llyrios-MacBook-Pro:~ llyrioboateng$ nslookup -type=txt debug.opendns.com.

    Server: 208.67.222.222

    Address: 208.67.222.222#53

     

    Non-authoritative answer:

    debug.opendns.com text = "server m6.lon"

    debug.opendns.com text = "flags 20 0 50 3950000000000000000"

    debug.opendns.com text = "originid 74005773"

    debug.opendns.com text = "actype 2"

    debug.opendns.com text = "bundle 9698311"

    debug.opendns.com text = "source 92.19.170.58:57101"

     

    Authoritative answers can be found from:

     

    Llyrios-MacBook-Pro:~ llyrioboateng$ netsh interface ipv4 show config

    0
    Comment actions Permalink
  • Avatar
    Llyrio

    Llyrios-MacBook-Pro:~ llyrioboateng$ netsh interface ipv4 show config

    -bash: netsh: command not found

    Llyrios-MacBook-Pro:~ llyrioboateng$ netsh interface ipv4 show config

    -bash: netsh: command not found

    Llyrios-MacBook-Pro:~ llyrioboateng$

     

    0
    Comment actions Permalink
  • Avatar
    rotblitz (Edited )

    No worries, the second command works on Windows only.  You didn't say that you have a Mac...
    A similar command on Mac OS X would be:  ifconfig -all

    Server: 208.67.222.222
    Address: 208.67.222.222#53

    Do you have these OpenDNS addresses configured directly on the Mac?  Or are these propagated by your router? 

    In the first case, configure the computer to obtain DNS server addresses automatically from the router, or configure the router's IP address as the only DNS server address.  Do this with any other devices too.

    In the second case you must take special measures of the following kind to circumvent or allow for internal name resolution:

    • As I said already, try to access your devices by their internal IP addresses instead of by their network names.
    • If this is not possible, because the devices expect to be called by their network name, then you can use the local hosts files on the client devices to configure the devices you need to access by their network name.
    • There are other measures like an own internal DNS and DHCP server or a second router, but not sure if you want to go this way.

    Most of those also require static internal IP addresses or DHCP reservations for all devices you want to connect to.

    "all of my computers including the bosesoundtouch devices didn't have any internet access."

    I doubt this.  As can be seen from your command output, you do have internet access also with using OpenDNS.

    "I didn't have any family restrictions in place. It was set as none."

    This is irrelevant, because nothing seems to have been blocked by OpenDNS, else you would have been presented with the OpenDNS block page.  I presume that your problems are related only to internal name resolution, as I have explained above.

    0
    Comment actions Permalink

Please sign in to leave a comment.