On Tue, Jan 20, 2015 at 07:39:22AM -0500, R. Clayton wrote: > I'm on this > [cut] > > server 0.debian.pool.ntp.org iburst > server 1.debian.pool.ntp.org iburst > server 2.debian.pool.ntp.org iburst > server 3.debian.pool.ntp.org iburst > [cut] > > this happens > > $ ntpq -p > remote refid st t when poll reach delay offset jitter > ============================================================================== > clock.monmouth. .INIT. 16 u - 64 0 0.000 0.000 0.000 > > $ > > Why aren't any specified servers in use? > Why the unspecified clock.monmouth server listed? I'm not sure why you only have only one source available, but I'd check that you're not blocking UDP port 123. Just because you can ping a server, doesn't necessarily mean that the protocol you want can get through. As for where "clock.monmouth." comes from, NTP will perform a reverse DNS lookup on a remote host in order to find out which member of a pool you've reached. That is, the **.pool.ntp.org hosts are round-robin hosts; a lookup of those names will return an arbitrary member of the set of hosts. NTP will then look up the hostname of the IP that was returned and this will typically yield the "real" name of the machine.
Attachment:
signature.asc
Description: Digital signature