Problems with ntp4.2 when names resolve to IPv6 addresses

[Kevin Oberman]

After the update of ntp in CURRENT to 4.2.0, my systems stopped working
because the servers specified in ntp.conf had AAAA records associated
with them. If the IPv6 address is not reachable, ntpd does not seem to
give up and try the IPv4 address. It looks to me like it just gives up.

I did not notice any problem while I was on an IPv6 connected network at
work or while on travel at a networking conference as they have IPv6
connectivity, but when I tried from home, where my broadband provider
does not provide any IPv6 routing, ntp simply spits out messages that it
failed to connect to each server.

Is this a problem with the vendor code or is it the result of some
FreeBSD patch?
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman at es.net			Phone: +1 510 486-8634