NTP error logs produced in May 2020

book

Article ID: 192198

calendar_today

Updated On:

Products

Content Analysis Software - CA

Issue/Introduction

In May 2020, devices pointing to ntp.bluecoat.com, ntp1.bluecoat.com, or ntp2.bluecoat.com experienced errors in syncing NTP. By default Content Analysis is configured to use ntp.bluecoat.com and ntp1.bluecoat.com. 

If your default was set to ntp1.net.symantec.com, ntp2.net.symantec.com or ntp3.net.symantec.com, errors will still be present

Cause

NTP server shutdown

Resolution

On May 28th the NTP service was restored by changing the pointer of ntp.bluecoat.com, ntp1.bluecoat.com, ntp2.bluecoat.com to time.google.com.

Anyone who has hard-coded the previously used IP of ntp.bluecoat.com and ntp2.bluecoat.com (63.245.205.123) will need to update their firewall rules to allow the new IPs.

If your NTP is using any of the hosts at symantec.com, please change them to the bluecoat server or to any server you wish to use by going to Settings > NTP; in the user interface, be sure to remove the symantec.com hosts to prevent additional errors.

Additional Information

ntp.bluecoat.com        canonical name = time.google.com.
Name:   time.google.com
Address: 216.239.35.4
Name:   time.google.com
Address: 216.239.35.8
Name:   time.google.com
Address: 216.239.35.12
Name:   time.google.com
Address: 216.239.35.0