On Wed, 24 May 2023 at 02:01, Jakob Bohm
wrote:
> For more rapid testing, could you describe the particular failing
> getaddrinfo() behavior and perhaps provide a sample command line C
> program that tests it in isolation instead of forcing each tester to
> run through a long ntpd run (usually
On 2023-05-22 05:53, Dave Hart wrote:
...
This appears to be a bug in Windows 11 resolving hostnames to IP addresses.
I would love to hear from others if they are seeing similar behavior on
Windows ntpd with a similar pool configuration. I'm using Windows
11 22H2 (22621.702) x64. I'm
I recently visited a relative who, unlike myself, has IPv6 service from her
ISP. I noticed ntpd on my Windows laptop configured with:
pool 2.pool.ntp.org
was not soliciting any IPv6 pool servers. For those unfamiliar, the 2.*.
pool.ntp.org names are the only ones which return IPv6 addresses
as
