| Re: [chrony-users] hostnames vs. IP address in chrony.conf |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
On 31/10/2012 13:52, Tomalak Geret'kal wrote:
So we're concluding that chrony as an application will never be able
to use the Domain Name System properly? That seems like an incredible
design hole if we are to be able to provide domain names in the config
at all.
I think you are picking your own definition of "properly". NTP is not
TCP, but it has a long term behaviour which looks something like a TCP
connection, ie fixed endpoints communicating with something approaching
"state"
eg:
- My email program (Thunderbird) does DNS resolution at initial
connection, thereafter it can sit with the connection open for days and
ignores any change of DNS in the meantime. Arguably this is a problem
for people trying to load balance using DNS or take servers down for
maintenance...
- My browser (Firefox) does DNS resolution at initial connection,
thereafter it will not check DNS for at least 60 seconds (no matter if
the TTL is shorter), and it will not change the connection end point
mid-way through a long download, ie if the DNS changes mid-way through a
2 hour download, the browser does not drop the connection and reconnect
to the new end point
I could go on with examples from other protocols, but it seems a bit
pointless. NTP doesn't use the TCP protocol, but it is designed to have
state at the client end and have a long term persistent conversation
with the server to which that state applies.
From that point of view I think the current behaviour makes sense?
Kind regards
Ed W
--
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.