OpenDNS is no longer allows to Linkedin access?

Comments

3 comments

  • Avatar
    rotblitz (Edited )

    "OpenDNS is no longer allows to Linkedin access?"

    This sentence is nonsense.  There is no default blocking of such top domains.

    Also, https://www.privatetunnel.com/ is pretty expensive.  You may want to try a free VPN service like https://windscribe.com/

    An alternative DNS service (like OpenDNS) can only help to circumvent restrictions which are DNS based, not any other restriction methods like proxies, transparent caches or DPI.

    Your browser error message indicates that you blocked LinkedIn with your (or another user's) dashboard settings and didn't download the Cisco root CA certificate.
    https://support.opendns.com/hc/en-us/articles/227988787
    Ensure that you don't block LinkedIn at your dashboard, e.g. by selecting categories Jobs/Employment, Social Networking.  Also ensure that your IP address is registered at https://dashboard.opendns.com/settings/ or not registered at all.

    If this does not help, I would need more information.  Copy & paste the complete plain text output of the following diagnostic commands to here when using OpenDNS:

    nslookup -type=txt debug.opendns.com.
    nslookup whoami.akamai.net.
    nslookup www.linkedin.com.

     

  • Avatar
    alexei.mifrill.strizhak
    rotblitz thank you for help.
     
     
    Unfortunately, it does not help:
     

    ```

    mifrill@mifrill-desktop:~$ nslookup -type=txt debug.opendns.com.
    Server: 127.0.0.53
    Address: 127.0.0.53#53

    Non-authoritative answer:
    debug.opendns.com text = "server m7.ams"
    debug.opendns.com text = "flags 20 0 70 180000000000000000007950800000000000000"
    debug.opendns.com text = "originid 0"
    debug.opendns.com text = "actype 0"
    debug.opendns.com text = "source 5.3.116.62:3086"

    Authoritative answers can be found from:

    mifrill@mifrill-desktop:~$ nslookup whoami.akamai.net.
    Server: 127.0.0.53
    Address: 127.0.0.53#53

    Non-authoritative answer:
    Name: whoami.akamai.net
    Address: 2620:0:cc4::17

    mifrill@mifrill-desktop:~$ nslookup www.linkedin.com.
    Server: 127.0.0.53
    Address: 127.0.0.53#53

    Non-authoritative answer:
    Name: www.linkedin.com
    Address: 5.3.3.17
    Name: www.linkedin.com
    Address: 2a02:2698:a002:1::3:17

    ```

  • Avatar
    rotblitz (Edited )

    This confirms that you're using OpenDNS (data center Amsterdam) and that your IP address 5.3.116.62 is not registered at OpenDNS.

    However, it looks like your ISP (ertelecom.ru) intercepts your DNS traffic and redirects you to another own destination for certain domains like www.linkedin.com.

    Name: www.linkedin.com
    Address: 5.3.3.17
    Name: www.linkedin.com
    Address: 2a02:2698:a002:1::3:17

    These are ertelecom.ru IP addresses, not LinkedIn addresses.   Contact your ISP to opt out from this interception.  Or threaten them with not paying your bills.  This is not the "service" you want and pay for!

    If this is to no avail, try to use DNSCrypt (https://dnscrypt.info/implementations) with OpenDNS (the service is called "cisco") which may be able to circumvent the restriction if you send your DNS traffic over ports 443 or 5353 instead of 53 and maybe use only TCP instead of UDP/TCP.

    Or try this trick with the local hosts file on your computer by adding these entries:

    108.174.10.10  linkedin.com
    2620:109:c002::6cae:a0a linkedin.com
    185.63.145.1 www.linkedin.com
    2a05:f500:10:101::b93f:9101 www.linkedin.com
    95.100.198.121 media.licdn.com
    2606:2800:234:16ec:2f0:2555:1cb5:1a57 media.licdn.com
    95.100.198.121 static.licdn.com
    2a02:26f0:eb:3a3::25ea static.licdn.com
    192.229.133.150 platform.linkedin.com
    2a02:26f0:eb:39d::25eb platform.linkedin.com

    You can leave the IPv6 entries out if you don't have IPv6 connectivity.

Please sign in to leave a comment.