| Antwort: Re: [chrony-users] Repeated 'refresh'es may cause excessive DNS queries |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Antwort: Re: [chrony-users] Repeated 'refresh'es may cause excessive DNS queries
- From: t.barnewski@xxxxxx
- Date: Wed, 13 Mar 2024 10:11:30 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/simple; d=avm.de; s=mail; t=1710321090; bh=dDhduNNeqEJ+Cchinkkbr95mty69UO8t1jmQ3Tc3sUs=; h=In-Reply-To:References:Subject:From:To:Date:From; b=OZG4HttpE5xAtIc073y0ohgHMTfiXkFSAavQI2BExCSprv3V4f/bhxhuGKv84LIu1 V6sVr0RrtBWSuol0evmOfEsRs2AigwFvveHvcNdgXs/qaM61aDoOGskwlCX5nzqVda al+k++CtLxq/jiNLEB2CCuXtI9V7PSOfumlnASwM=
- Sensitivity:
Hi Matt,
> What happens if you add '-4' to your Chrony process? Looking at the
> logs, it appears your system is unable to connect to an IPv6 address.
> After it tries several times, it finds a IPv4 address and syncs.
> This may be a problem with your docker setup or host system, regardless
> adding the '-4' flag should prevent Chrony from trying the IPv6 address.
This is purely an artifact of my local test setup, which I set up with
IPv4 only since I'm lazy...eh, I mean for simplicity.
In any case, the problem persists if I add -4 to the chronyd command line.
The only observable difference is that chrony no longer queries AAAA records,
but it still fires dozens or even hundreds of requests for A records.
The problem also persists if I enable IPv6 on both machines.
Regards,
Tim
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.