Sonic,
I can confirm same issue on -current when ntpd tries to use AAAA
record to resolve constraints IP address.
Can you check and confirm if you don't have IPv6 address :)
I guess you should have at least link-local and loopback IPv6 addresses :)
ifconfig | grep inet6
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
# cat /etc/ntpd.conf
# $OpenBSD: ntpd.conf,v 1.14 2015/07/15 20:28:37 ajacoutot Exp $
#
# See ntpd.conf(5) and /etc/examples/ntpd.conf
#servers pool.ntp.org
#sensor *
constraints from "https://www.google.com";
# ntpd -d -s -v
ntp engine ready
set local clock to Tue May 31 20:51:36 EEST 2016 (offset 0.000000s)
tls connect failed: 2a00:1450:401b:801::2004 (www.google.com):
connect: No route to host
no constraint reply from 2a00:1450:401b:801::2004 received in time,
next query 900s
constraint reply from 173.194.113.211: offset -0.803262
On Tue, May 31, 2016 at 6:36 PM, Sonic <sonicsm...@gmail.com> wrote:
> 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
>
--
--
With regards,
Eugene Sudyr
