Am 05/31/16 um 18:36 schrieb Sonic:
> Getting many such log entries:
> =======================
> May 31 08:53:34 stargate ntpd[5702]: tls connect failed:
> 2607:f8b0:4009:808::2004 (www.google.com): connect: No route to host
> May 31 09:08:35 stargate ntpd[15803]: tls connect failed:
> 2607:f8b0:4009:808::2004 (www.google.com): connect: No route to host
> May 31 09:23:36 stargate ntpd[92515]: tls connect failed:
> 2607:f8b0:4009:808::2004 (www.google.com): connect: No route to host
> =======================
>
> ntpd.conf has the line: constraints from "https://www.google.com";
>
> System has no ipv6 addresses. Unbound is resolving DNS server with "do-ip6:
> no".
>
> resolv.conf uses "nameserver 127.0.0.1" (Unbound serving on this address)
>
> normal lookups (dig) only return the ipv4 address for www.google.com
>
> Why does ntpd attempt to connect on an ipv6 address?
>
> Thanks,
>
> Chris
>
I asked this just last week. Carlin Bingham's answer solved the issue
for me (http://article.gmane.org/gmane.os.openbsd.misc/231185):
In /etc/resolv.conf, add:
family inet4
(Well: I actually added it in /etc/resolv.conf.tail ...)
Best,
STEFAN
