Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 22 replies
  • Subscribers 1 subscriber
  • Views 77381 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Mac: Could not contact primary server

xdunlapx

I tried updating my Sophos AV on my mac and it says that it ould not contact the primary server and the error occured today 23 Sep 2012 15:44. Is this related to the fase-positive issue? How long should I wait before trying to update my definitions again? Should I remove and reinstall it?

Brittany

:32639


This thread was automatically locked due to age.
Parents
  • 0
    The update failures appear to be caused by a change in our CDN (content distribution network). Our operations group is continuing to work the issue, it appears perhaps that the affected systems may be using stale DNS entries for our servers (dci.sophosupd.com, d1.sophosupd.com, d2.sophosupd.com should no longer resolve to Akamai servers).
     
    We aren’’’’t certain why this phenomenon is occurring, but it may be due to infrastructure that is incorrectly caching DNS names. One good test is to run “dig dci.sophosupd.com” to see if it returns a CNAME for “sophos.vo.llnwd.net” - if not, the DNS record is stale.
     
    We are interested to understand whether this is really the root cause or not. Try the command on an affected machine and post the results back here.
    :56362
Reply
  • 0
    The update failures appear to be caused by a change in our CDN (content distribution network). Our operations group is continuing to work the issue, it appears perhaps that the affected systems may be using stale DNS entries for our servers (dci.sophosupd.com, d1.sophosupd.com, d2.sophosupd.com should no longer resolve to Akamai servers).
     
    We aren’’’’t certain why this phenomenon is occurring, but it may be due to infrastructure that is incorrectly caching DNS names. One good test is to run “dig dci.sophosupd.com” to see if it returns a CNAME for “sophos.vo.llnwd.net” - if not, the DNS record is stale.
     
    We are interested to understand whether this is really the root cause or not. Try the command on an affected machine and post the results back here.
    :56362
Children
No Data