Sonic <sonicsm...@gmail.com> writes: > 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?
ntpd(8) doesn't use getaddrinfo+AI_ADDRCONFIG, which is supposed to skip DNS requests for IPv6 if the machine doesn't have IPv6 addresses configured. An IPv4 connectivity problem may lead ntpd to fall back to trying IPv6. See the resolv.conf(5) "family" keyword for a way to disable IPv6 DNS requests. -- jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
