The local clock fudge is just to force it down to stratum 10, i.e. as a last resort so that local clients can still sync. if I loose the internet connection (Fedora core 3 default).
The ntpq output shows that, as far as ntpd is concerned, uk.pool.ntp.org = 184.108.40.206, period. The first two entries show as unreachable because they are duplicates of the only functioning server entry.
My "normal", hard-coded configuration is:
server 220.127.116.11 maxpoll 12
server 18.104.22.168 maxpoll 12
server 22.214.171.124 maxpoll 12
server 127.127.1.0 # local clock
fudge 127.127.1.0 stratum 10
The addresses were chosen from the uk pool. This usually reports something like:
# ntpq -pn
remote refid st t when poll reach delay offset jitter
+126.96.36.199 188.8.131.52 2 u 62m 68m 377 23.814 -2.221 3.211
*184.108.40.206 .MSF. 1 u 62m 68m 377 37.137 1.519 1.475
+220.127.116.11 18.104.22.168 4 u 62m 68m 377 16.469 -1.183 2.727
127.127.1.0 LOCAL(0) 10 l 54 64 377 0.000 0.000 0.004
... just as one would expect. The maxpoll 12's are there to further reduce server polling to less than one per hour if conditions permit.
I could just cary on with the "manual" configuration but I don't want to keep picking on the same three servers when there's a better solution, i.e. the ntp pools. I just can't get ntpd to come up with round-robin addresses, and I hate not knowing why.
Thanks for the suggestions and the prompt response! Thanks also for donating your bandwith to the world of ntp.