| Re: 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: Re: Re: [chrony-users] Repeated 'refresh'es may cause excessive DNS queries
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Thu, 14 Mar 2024 16:45:49 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1710431167; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=d1qeBqG83lfFJa358LcqdUQ1Hp5RCkZC+dI+7RGNrzs=; b=Q/LEOIPPniRA3+mpV6yq05ksqPBsfu3SudcJ0kAW9RqmIQWMOkbqWsw/JKDDHHxSVM4Qjp x6p+V37dsbJwJURii61u+3RRZYF1phM5pSm6iTw8bepSCuPewzti+SADex1DYMjLBqDC3q G6rCjv394Dvwmed0jl0WtqzDsCLMMq4=
On Wed, Mar 13, 2024 at 02:05:06PM +0100, Miroslav Lichvar wrote:
> I think I see what is happening now. The config specifies a pool which
> means 4 servers by default. You override the real DNS record with a
> single IPv4 server. IPv6 is disabled or unreachable. chronyd resolves
> the name and gets only one working IP address. It doesn't remove the
> name from the resolving queue in order to get the 3 missing addresses.
> When you make the refresh command, the name of the unresolved sources
> is added to the queue again, but that doesn't provide a new address,
> so they stay there and the queue accumulates duplicated resolving
> requests.
>
> I'll fix that.
It should be now fixed in git. Thanks for the report.
--
Miroslav Lichvar
--
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.