Re: Re: Repeated 'refresh'es may cause excessive DNS queries
Miroslav Lichvar <[email protected]>
| Newsgroups | gmane.comp.time.chrony.user |
|---|---|
| Message-ID | <ZfMbra4pvuDg51ij@localhost> |
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-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org with "unsubscribe" in the subject. For help email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org with "help" in the subject. Trouble? Email [email protected]