[ 2018-02-20 08:58 ] We've started troubleshooting a problem were STO1 is unable to access
Google DNS servers.
[ 2018-02-20 10:26 ] We have a high priority case with Cisco and continues the troubleshooting together with Cisco engineers.
[ 2018-02-20 11:46 ] The troubleshooting is still ongoing. As a temporary workaround you could change DNS server to 220.127.116.11. If you face any problems changing to this IP, please contact the support. Note that this is only a temporary workaround!
[ 2018-02-20 13:20 ] We've received a suggested fix from the Cisco engineers. As the fix increases the risk of network disturbance, the fix will be applied during tonights scheduled service window. In the meantime we suggest that you use 18.104.22.168 as DNS server.
[ 2018-02-20 18:02 ] All Google DNS servers are accessible again. If you are already using the temporary dns server 22.214.171.124 we recommend you to continue to do that until tomorrow. We are applying fixes tonight to prevent this from happening in the future.
[ 2018-02-20 18:02 ] Configuration to prevent this from happening again is in place. If you switched from Google dns servers it is now safe to switch back and use the Google dns servers again.