Comments

10 comments

  • Avatar
    rotblitz

    Post the complete plain text output of the following commands:

    nslookup -type=txt debug.opendns.com.

    tracert 208.67.222.222

    0
    Comment actions Permalink
  • Avatar
    maninho

    nslookup -type=txt debug.opendns.com

    unrecognized command:  nslookup -type=txt debug.opendns.com

     

    tracert 208.67.222.222

    Servidor= [208.67.222.222]

    Não é resposta de autorização:

    Nome: tracert

    Address: 67.215.65.132

    0
    Comment actions Permalink
  • Avatar
    rotblitz

    Weird, this is of minor use.  In case you have Linux or Mac OSX, use these commands instead:

    dig debug.opendns.com txt

    traceroute 208.67.222.222

    If you have Windows, then open a command prompt window to enter the commands from above, exactly as I have written them.

    0
    Comment actions Permalink
  • Avatar
    maninho

    Rotblitz, I have entered the commands in a command prompt exactly as you wrote them, the above lines are the exact output that appeared on the command window (my Windows 7 Home Premium is a Brazilian localized version).

    But after trying that, I experimented with changing the OpenDNS servers to those of GoogleDNS and had the same problem, so I no longer  think that it's an OpenDNS problem. The sites that give me the problem are related to www.pcmag.com 2nd level links, everything else works OK.

    0
    Comment actions Permalink
  • Avatar
    rotblitz

    "I have entered the commands in a command prompt exactly as you wrote them"

    No, you didn't.  You entered just "nslookup" and were landing on the nslookup subprompt.  Then you entered the command "nslookup -type=txt debug.opendns.com." at the subprompt.  And then you entered "tracert 208.67.222.222" at the nslookup subprompt too.  This is not going to work, but will exactly produce the useless output I see!  What you did (as it clearly says), you first entered an "unrecognized command", and then you queried the hostname "tracert" at OpenDNS which returned 67.215.65.132 (hit-nxdomain.opendns.com).

    "The sites that give me the problem are related to www.pcmag.com 2nd level links"

    This dramatically changes the picture from "Some sites hang looking for "w10.guidetest.b.10.opendns.com", in Firefox, IE and Chrome" and is totally different...

    If you switch back to OpenDNS, I would need to see the following command outputs then:

    nslookup -type=txt debug.opendns.com.

    tracert 208.67.222.222

    nslookup www.pcmag.com.

    0
    Comment actions Permalink
  • Avatar
    rotblitz

    ...and also:

    tracert www.pcmag.com

    0
    Comment actions Permalink
  • Avatar
    maninho

    OK, I stand corrected <g>

    Here's the output:

    C:\Users\Wilson>nslookup -type=txt debug.opendns.com
    Servidor:  my.router
    Address:  192.168.2.1

    Não é resposta de autorização:
    debug.opendns.com       text =

            "server 5.ams"
    debug.opendns.com       text =

            "flags 20 0 2f4 4000800000000000000"
    debug.opendns.com       text =

            "id 0"
    debug.opendns.com       text =

            "source 187.127.27.233:2053"

     

    C:\Users\Wilson>tracert 208.67.222.222

    Rastreando a rota para resolver1.opendns.com [208.67.222.222]
    com no máximo 30 saltos:

      1    <1 ms    <1 ms    <1 ms  my.router [192.168.2.1]
      2     1 ms     1 ms     1 ms  192.168.1.1
      3    16 ms    13 ms    13 ms  200-217-90-96.host.telemar.net.br [200.217.90.96]
      4    16 ms    16 ms    19 ms  xe-6-1-0.0-mpi-mg-rotn-j01.telemar.net.br [200.164.13.123]
      5    45 ms    22 ms    22 ms  so-1-1-0.0-arc-rj-rotn-j01.telemar.net.br [200.223.45.165]
      6   146 ms   147 ms   148 ms  200.164.11.102
      7   223 ms   222 ms   234 ms  mia1-cr1-te2-1-0.cprm.net [195.8.30.221]
      8   225 ms   222 ms   223 ms  lis1-cr1-te0-0-2.cprm.net [195.8.0.177]
      9   248 ms   246 ms   244 ms  ams1-cr1-te1-4-0.cprm.net [195.8.0.230]
     10   240 ms   241 ms   245 ms  peer1.rtr1.ams.opendns.com [195.69.144.88]
     11   244 ms   244 ms   246 ms  resolver1.opendns.com [208.67.222.222]

    Rastreamento concluído.

    C:\Users\Wilson>

    C:\Users\Wilson>nslookup www.pcmag.com
    Servidor:  my.router
    Address:  192.168.2.1

    Não é resposta de autorização:
    Nome:    a390.g.akamai.net
    Addresses:  200.149.150.138
              200.149.150.145
    Aliases:  www.pcmag.com
              www.pcmag.com.edgesuite.net


    C:\Users\Wilson>

    C:\Users\Wilson>tracert www.pcmag.com

    Rastreando a rota para a390.g.akamai.net [200.149.150.145]
    com no máximo 30 saltos:

      1    <1 ms    <1 ms    <1 ms  my.router [192.168.2.1]
      2     1 ms     1 ms     1 ms  192.168.1.1
      3    14 ms    13 ms    13 ms  200-217-90-96.host.telemar.net.br [200.217.90.96]
      4    15 ms    14 ms    13 ms  xe-6-1-0.0-hga-mg-rotn-j01.telemar.net.br [200.164.13.121]
      5    25 ms    23 ms    24 ms  so-9-1-0.0-arc-rj-rotn-j01.telemar.net.br [200.223.45.169]
      6    22 ms    25 ms    26 ms  200164040073.user.veloxzone.com.br [200.164.40.73]
      7    24 ms    21 ms    22 ms  200.164.201.182
      8    23 ms    22 ms    22 ms  200.223.55.130
      9    21 ms    22 ms    23 ms  200.149.150.145

    Rastreamento concluído.

    C:\Users\Wilson>

    0
    Comment actions Permalink
  • Avatar
    rotblitz

    Nearly everything's fine, but your dashboard settings will not be used, because your IP address 187.127.27.233 is not registered with your OpenDNS network. 
    https://dashboard.opendns.com/settings/

    Another observation is that you use the OpenDNS Amsterdam location.  Bad routing by your ISP and the peering network carriers...

    0
    Comment actions Permalink
  • Avatar
    maninho

    Just an update: It seems the problem is with a change on the PcMag.com site itself; when I access it, they now recognize by my IP that I'm in Brazil, and switch me to their site in Portuguese (PcMag.com.br); but the second-level link adresses get broken. In the same way, when I logon on their Brazilian site, the links to the US site archives get broken. If I use the Tor browser, which reroutes my IP, everything works OK both ways. As this started happening only recently, I guess they have changed something but slipped up... I wrote them to report the problem.

    Thank you for your advice on OpenDns.

    0
    Comment actions Permalink
  • Avatar
    rotblitz

    This makes perfectly sense.

    0
    Comment actions Permalink

Please sign in to leave a comment.