M Graff wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Tony Hoyle wrote: > >> As ipv6 usage grows more servers come online, so it >> should never get to the point that ipv6.pool.ntp.org gets flooded. > > If we use a name like ipv6.pool.ntp.org, we have lost.
If we don't, we get large scale breakage. Too many things like linux distros (and osx, and vista) ship with ipv6 enabled, but the users don't have external routing. Web browsers cope with this by retrying both (hence the often repeated comment that having ipv6 enabled 'slows down the internet'). NTP doesn't do this... it just assumes that the address it got is currently dead (and it has no way of doing it because it only does the dns lookup when it starts up).. which makes sense for the way ntp works but means that it's going to be permanently dead. If it picks up 3 of those then you have the situation that suddenly you broke someones NTP completely. Yes you could get 3 dead pool addresses but that's unlikely because the pool monitoring takes dead servers out of rotation for precisely this reason. > You seem to be one of those people who has to keep IPv6 and IPv4 apart > in their minds. They are completely separate protocols! They can't even talk to each other. Tony _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
