>This makes ntpd very unhappy, as it can't reach the remote servers anymore.
>As a workaround I'm killing and restarting ntpd in my ip-up script, but I'm
>wondering what the real solution would be.

a better solution would be for ntpd use an ephemeral port for talking
to servers, just like ntpdate does, and then to close it after it's
done with a round of polling.  just my opinion.

im(ns?)ho, ntpd should *also* periodically re-lookup the addresses for
hostnames that are its peers/servers.  i have had several annoying
situations where a host's address changed, the ntp.conf was correct on
a client/peer, and the host's time slowly drifted *anyway*.  ntpd just
needs to be restarted, but it's a pain.

-- 
|-----< "CODE WARRIOR" >-----|
codewarrior@daemon.org             * "ah!  i see you have the internet
twofsonet@graffiti.com (Andrew Brown)                that goes *ping*!"
andrew@crossbar.com       * "information is power -- share the wealth."