Comments

11 comments

  • Avatar
    apluswebmaster

    @waynepp

    Without you saying so, I bet you are using a Win7 system. For me (getting the same msg after login), it's just simply another "Windows annoyance" - no biggie.

    They'll likely fix it somewhere down the road, when they feel they don't have anything better to do. I'd also bet everything else on your machine is just running fine...

    .

     

    0
    Comment actions Permalink
  • Avatar
    waynepp

    yep windows 7 and all good, just a niggle more than anything

    0
    Comment actions Permalink
  • Avatar
    Kristy Patullo

    This is due to the OS calling out to the domain ipv6.microsoft.com. OpenDNS is trying to resolve it, but the domain does not respond to our resolvers, which causes Windows to alert the user that they may need to update their login credentials, because it's assuming you haven't connected to the Internet.

    The issue should be fixed now, please flush your browser and DNS cache by following the instructions below:

    http://www.opendns.com/support/article/67
    http://www.opendns.com/support/article/68

    0
    Comment actions Permalink
  • Avatar
    matth79

    It was fixed, but now it's back to showing the redirect page again - this domain MUST NOT REDIRECT!

    0
    Comment actions Permalink
  • Avatar
    waynepp
    Yeah started popping up on my Windows machines again too :(
    0
    Comment actions Permalink
  • Avatar
    Kristy Patullo

    @matth79 'It was fixed, but now it's back to showing the redirect page again - this domain MUST NOT REDIRECT!' ipv6.microsoft.com is showing the guide page? Can you please clarify what you mean by this domain is redirecting?

    0
    Comment actions Permalink
  • Avatar
    matth79

    Yes, the guide page - if that comes up (for ipv6.msftncsi.com) then NCSI thinks it's a login page - it has three possible conditions.

    1. Receive the correct text back - success

    2. Receive NXdomain for the domain / HTTP error for the page - no connection.

    3. Anything else, - might be login page, so pop stupid message up!

    0
    Comment actions Permalink
  • Avatar
    Kristy Patullo

    Thanks for the clarification, we are looking into this.

    0
    Comment actions Permalink
  • Avatar
    maintenance

    For an immediate temporary fix, add  ipv6.msftncsi.com to your Typo Exceptions (and flush caches).  That should cover any of the subdomains like teredo or 6to4.

    Weird note, there is no SOA for the zone. Maybe there is some technical Microsoft reason for this.

    0
    Comment actions Permalink
  • Avatar
    rotblitz

    CNAMEs do not necessarily return an SOA. ipv6.msftncsi.com is a CNAME for ipv6.msftncsi.com.edgesuite.net which returns an SOA and again is a CNAME for a978.i6g1.akamai.net. The latter returns an SOA record and also two AAAA records, but no A record. These facts cause OpenDNS to return the IP address of hit-nxdomain.opendns.com for an A record query.

    Bad enough that the OS's NCSI attempts to raise an A query against ipv6.msftncsi.com at all.  Queries should be restricted to AAAA.

    0
    Comment actions Permalink
  • Avatar
    maintenance

    Bad enough that there is such a thing. I rather expect that people know if they are connected to the internet or not.

    0
    Comment actions Permalink

Please sign in to leave a comment.