Hello,
Sam C. Nicholson !! wrote:
Point your client toward the servers that you point your
server toward, if you can. See which doesn't work.
I trust you've already checked that your server is chiming
the correct time from its upstream clocks.
It works fine with the time server of my ISP I sync my server from, and my
server also syncs the correct time from that server.
Darren Tucker wrote:
That's the OpenNTPD server rather than the reference you're trying to
sync the OpenNTPD server to? If so it appears normal, the only
potential issue I see is that it has a relatively high stratum of 5.
I would guess that the Windows client you're trying to use rejects the
reference because of the stratum. (There's no particularly good
reason for that, even at stratum 5 it should easily be accurate within
a hundred milliseconds; right now it's 30ms or so). If that's the
case then your options are a) use a lower stratum reference source on
the OpenNTPD server (such as the public stratum 2 "pool" servers) so
its stratum is lower, or b) use a different NTP client on your Windows
box.
You can accomplish a) by replacing the "server" and "servers"
directives in your ntpd.conf with simply "servers hu.pool.ntp.org".
I did find an apparent DNS problem with this service: one of the DNS
servers (ns2.t-hosting.hu) returns NXDOMAIN for time.t-hosting.hu.
The other is OK.
Constantine A. Murenin wrote:
OpenNTPD 3.6.1 had some problems with stratum calculations... It was
fixed in the latest version, 3.7. Try to use the latest version, 3.7,
and then see if the problem still exists.
I haven't change the source server so far, because I've upgraded to 3.7
and have
tried to sync the Windows client to the server. I've experienced three
cases with the
new version:
1, The synchronization fails due to the stratum.
2, The synchronization succeeds.
3, The synchronization fails with error message: peer is unreachable.
As I've experienced, after starting the server there is a period when
the first case happens,
and after a while the synchronization mostly succeeds. The third case
was rare.
Is this the normal behaviour?
As for the DNS problem, thanks. I don't know what's wrong, however. I did a
named reload after modifying the zone file, and there's the notify support
between the two nameservers.
Cheers,
Gabor Kvvesdan
