I have DMZ server configured as NTP server to connect to external NTP servers and sync time in all devices in my corporate network. Below are the contents of my ntp.conf file in the DMZ server
server 127.127.1.0
fudge 127.127.1.0 stratum 6
driftfile /var/lib/ntp/ntp.drift
logfile /var/log/ntpd.log
statistics loopstats peerstats clockstats
filegen loopstats file loopstats type day enable
filegen peerstats file peerstats type day enable
filegen clockstats file clockstats type day enable
server 0.asia.pool.ntp.org iburst
server 1.asia.pool.ntp.org iburst
server 2.asia.pool.ntp.org iburst
server 3.asia.pool.ntp.org iburst
server time.google.com iburst
restrict -4 default kod nomodify notrap
restrict 127.0.0.1
restrict ::1
However, there is a 27 seconds difference with the local time in UAE (timezone server is in) and the server "date". I executed below commands and reboots of server, multiple times. This is a Debian 9.6 server. I did all package updates in server, still 27 seconds difference.
/etc/init.d/ntp stop
ntpdate -u 0.asia.pool.ntp.org
/etc/init.d/ntp start
hwclock -w
ntpq -p
ntpq -p output is as below:
~# ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
LOCAL(0) .LOCL. 6 l 709 64 0 0.000 0.000 0.000
-ntp.paina.net 131.113.192.40 2 u 30 64 377 220.331 31.973 0.491
-119.28.206.193 100.122.36.196 2 u 107 64 346 151.095 8.540 8.537
+uk.cluster.ntp. 185.134.196.169 2 u 28 64 377 133.718 -2.215 0.278
+t2.time.sg3.yah 106.10.133.18 2 u 28 64 377 95.837 5.051 0.602
*time2.google.co .GOOG. 1 u 30 64 377 163.875 -6.637 0.338