Re: Re: [chrony-users] Repeated 'refresh'es may cause excessive DNS queries

[Miroslav Lichvar <mlichvar@xxxxxxxxxx>]

On Tue, Mar 12, 2024 at 05:35:06PM +0100, t.barnewski@xxxxxx wrote:
> > That seems to be working for me as expected. I see one request per
> > refresh. Can you please build chronyd with --enable-debug and post the
> > chronyd -dd output for first few refresh commands?
> 
> I have attached the debug log after 4 refresh commands.
> chrony made about 320 DNS requests after those.

Ok, thanks.

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.

-- 
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.