Stephen Satchell wrote:
On 12/20/2017 11:51 AM, Rob Janssen wrote:
A time server that uses DNS based rules for reference servers should fail
gracefully when the DNS does not return
an IP address (anymore). So, when it does a lookup only once it should issue
an error message about that server,
Hi Rob, Bill
On 21/12/2017, at 9:20 AM, Bill Unruh wrote:
There are two questions here:
a) chrony drips a source if the dns does not deliver a valid IP for that
server.
b)What should the the underlying philosophical stance be of a program like
chrony to the use of DNS.
I was answering the f
William G. Unruh __| Canadian Institute for| Tel: +1(604)822-3273
Physics&Astronomy _|___ Advanced Research _| Fax: +1(604)822-5324
UBC, Vancouver,BC _|_ Program in Cosmology | un...@physics.ubc.ca
Canada V6T 1Z1 | and Gravity __|_ www.theory.physics.ubc.ca/
On Wed, 20 D
On 12/20/2017 11:51 AM, Rob Janssen wrote:
A time server that uses DNS based rules for reference servers should
fail gracefully when the DNS does not return
an IP address (anymore). So, when it does a lookup only once it should
issue an error message about that server,
and proceed its startup a
Hi Rob, Bill
> On 21/12/2017, at 9:20 AM, Bill Unruh wrote:
>
> There are two questions here:
> a) chrony drips a source if the dns does not deliver a valid IP for that
> server.
> b)What should the the underlying philosophical stance be of a program like
> chrony to the use of DNS.
>
> I was a
On 12/20/2017 12:20 PM, Bill Unruh wrote:
You have apparently implimented my suggestion as to how to solve that
question, despite your moral qualms about that implimentation.
Actually, I exchanged mail with the server administrators before moving
to IP-based specification for those server entr
There are two questions here:
a) chrony drips a source if the dns does not deliver a valid IP for that
server.
b)What should the the underlying philosophical stance be of a program like
chrony to the use of DNS.
I was answering the first, not the second. You had a problem, chronyd was
dropping se
Bill Unruh wrote:
In that list of servers, there is a field for each NTP time provider, "Use
DNS". Many of the public servers in this table require that DNS be used with their
service. Here is one entry from the table:
There is absolutely no way they would know if you are using dns or no
William G. Unruh __| Canadian Institute for| Tel: +1(604)822-3273
Physics&Astronomy _|___ Advanced Research _| Fax: +1(604)822-5324
UBC, Vancouver,BC _|_ Program in Cosmology | un...@physics.ubc.ca
Canada V6T 1Z1 | and Gravity __|_ www.theory.physics.ubc.ca/
On Wed, 20 D
William G. Unruh __| Canadian Institute for| Tel: +1(604)822-3273
Physics&Astronomy _|___ Advanced Research _| Fax: +1(604)822-5324
UBC, Vancouver,BC _|_ Program in Cosmology | un...@physics.ubc.ca
Canada V6T 1Z1 | and Gravity __|_ www.theory.physics.ubc.ca/
On Wed, 20 D
On 12/20/2017 09:01 AM, Bill Unruh wrote:
No idea if it will work, but you could put the IP address in instead of
names
for your servers-- that way no dns is needed.
Found the URL:
http://support.ntp.org/bin/view/Servers/StratumTwoTimeServers
In that list of servers, there is a field for ea
On 12/20/2017 09:01 AM, Bill Unruh wrote:
No idea if it will work, but you could put the IP address in instead of
names
for your servers-- that way no dns is needed.
I have longstanding arrangements with several NTP time sources. For
those sources, those that don't do load-sharing with DNS,
No idea if it will work, but you could put the IP address in instead of names
for your servers-- that way no dns is needed.
On Wed, 20 Dec 2017, Stephen Satchell wrote:
TL;DR: chronyd doesn't like server specifications with FQDN when there is no
DNS resolver available -- and neither does rival
TL;DR: chronyd doesn't like server specifications with FQDN when there
is no DNS resolver available -- and neither does rival ntpd. We'll see
if NXDOMAIN is just as bad.
(I did check to see if this had already been reported -- didn't find any
reference to issues like I experienced. Went back
14 matches
Mail list logo
