Bill Unruh <unruh@xxxxxxxxxxxxxx> wrote on 10/30/2012
15:45:14:
>
> On Tue, 30 Oct 2012, Tomalak Geret'kal wrote:
>
> > On 30/10/2012 19:21, Bill Unruh wrote:
> >> On Tue, 30 Oct 2012, Tomalak Geret'kal wrote:
> >>
> >> > Could chronyd not be made to pay attention to
the TTL of the IPs it
> >> > resolves?
> >> > That would /truly/ be "using IP to make that
association".
> >>
> >> What is the "TTL of the IPs it resolves"?
> > Let me be clearer, then.
> >
> > Every domain name has a TTL, short for "time to live".
When chrony
> resolves a
> > domain name to its IP, could it not be made to abide by this
TTL and
> > re-resolve the domain name when it expires? This is the way that
> every other
> > domain resolver in the world works, and is the fundamental underpinning
of
> > the Domain Name System.
>
> So you want to saddle chrony with a whole bunch of resolver software
as well?
> It is complex enough as it is ( remember that every addition to the
code
> doubles the probability of bugs.)
> Remember KISS.
I don't follow you here. Surely there isn't
a resolver of any kind in chronyd is there? I would expect nothing
more than a call to getaddrinfo() or getnameinfo() -- I know far more about
DNS resolution than the C library -- to be present in chronyd. All
of the actual DNS querying, /etc/host examination, caching and preference
handling should come automatically. To me, that would be KISS; like
let something else handle this.