[comp.protocols.time.ntp] xntpd selecting strange hosts to peer with

philip@beeblebrox.dle.dg.com (Philip Gladstone) (04/23/91)

I find that my xntpd sometimes picks 'strange' hosts to peer with. For
example:

     remote           refid      st  when poll reach  delay  offset   disp
==========================================================================
.127.127.8.0     .MSF.            0    34   64  376    11.8    0.11    1.0
.BITSY.MIT.EDU   .WWV.            1    23  128  357   497.8    9.12   31.4
 umd1.umd.edu    .WWVB.           1   277 1024  377   629.9   29.86  118.1
*dcn1.udel.edu   .ATOM.           1    23   64  377   635.3  -25.47   83.7
 otc1.psu.edu    .WWV.            1   158 1024  377   660.4   18.04  152.1
.pmax6.osf.org   .WWV.            1   588 1024  376   647.3  -90.55   43.7
.beeblebrox      .MSF.            1   758 1024  377    25.1    1.95    0.6
 127.127.1.4     127.127.1.1      4    37   64  377  5000.0    0.00    0.0

Is there an easy way to discover *why* it picked dcn1 rather than the
local radio clock or the local host 'beeblebrox'?

Philip

--
Philip Gladstone         Dev Lab Europe, Data General, Cambridge, UK

    Listen three eyes, don't you try and outweird me, I get
    stranger things than you free with my breakfast cereal.