[AusNOG] NTP Best Current Practices Internet Draft

Sean Agius sagius at pingco.com.au
Tue Feb 5 12:07:41 EST 2019

2019 is RTM now so there is at least 3 years of 2016; but most people are probably still on 2K8 R2 or 2K12(R2) (Being generous)…

The implementation of NT5DS and correctly setup PDCs have never been a problem for anyone, but that is more a sysadmin discussion.

Sean Agius
Senior Engineer
[cid:image001.jpg at 01D22EEE.8C7B7140]
Suite 114, 189 South Center Road, Tullamarine 3043

+61 3 8592 8866


sagius at pingco.com.au<mailto:sagius at pingco.com.au>


+61 431 236 571



This communication is intended only for use of the addressee and may contain legally privileged and confidential information. If you are not the addressee, you are notified that any transmission, distribution or replication of this message is strictly prohibited. The legal privilege and confidentiality attached to this email is not waivered, lost or destroyed by reason of a mistaken delivery to you. If you have received this message in error, we would appreciate immediate notification by telephone or return email and ask that the message be permanently deleted from your system.

From: AusNOG <ausnog-bounces at lists.ausnog.net> On Behalf Of Chris Barnes
Sent: Tuesday, 5 February 2019 9:52 AM
To: Paul Gear <ausnog at libertysys.com.au>
Cc: ausnog at lists.ausnog.net
Subject: Re: [AusNOG] NTP Best Current Practices Internet Draft

'stop flogging Microsoft for their decade and a half of shoddy implementation of internet time, their latest iteration finally works!'

Haha that's a good one.

On Mon., 4 Feb. 2019, 6:18 pm Paul Gear, <ausnog at libertysys.com.au<mailto:ausnog at libertysys.com.au>> wrote:
On 2/2/19 3:15 pm, Robert Hudson wrote:
> I say this as a long-time (since NT3.51) Windows sysadmin...
> On Sat, 2 Feb. 2019, 12:31 pm O'Connor, Daniel
> <darius-3tTUuF3Go8e6c6uEtOJ/EA at public.gmane.org<mailto:EA at public.gmane.org>
> <mailto:darius-3tTUuF3Go8emAE84gaIGEA at public.gmane.orgu<mailto:darius-3tTUuF3Go8emAE84gaIGEA at public.gmane.orgu>> wrote:
>     > On 2 Feb 2019, at 11:48, Mark Smith
>     <markzzzsmith-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org<mailto:markzzzsmith-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org>
>     <mailto:markzzzsmith at gmail.com<mailto:markzzzsmith at gmail.com>>> wrote:
>     > The problem that occurred with 0.au.pool.ntp.org<http://0.au.pool.ntp.org>
>     <http://0.au.pool.ntp.org> proving bad time
>     > wouldn't have had an effect if the Windows domain controller had at
>     > least 2 other NTP time sources.
>     The behaviour of OPs system implies that a PDC does not use more
>     than one clock source.
>     If that is true (I have no idea, but googling suggests it may be so)
>     then you are going to end up relying on a single time server. In
>     that case you are probably better firing up a tiny Linux VM running
>     only ntpd (or chrony etc etc) which is configured for multiple pool
>     servers and then point your DCs at that.
>     It does seem pretty ridiculous than Windows server can't behave more
>     sensibly though..
> The time service is the area where I felt Windows lagged significantly
> behind Linux more than any other. Why Microsoft still haven't adopted
> standardised tzdata and proper NTP is still, frankly, beyond me. The
> issues the Windows time services still cause are crazy...

I never thought I'd be the one doing this, but please, everyone - get
more accurate information before you bag Microsoft's time services.
They've made a lot of strides forward, and have offered a proper NTP
implementation since Server 2016:


AusNOG mailing list
AusNOG at lists.ausnog.net<mailto:AusNOG at lists.ausnog.net>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ausnog.net/pipermail/ausnog/attachments/20190205/919f053b/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 1730 bytes
Desc: image002.jpg
URL: <http://lists.ausnog.net/pipermail/ausnog/attachments/20190205/919f053b/attachment.jpg>

More information about the AusNOG mailing list