On 2017-12-18 06:44, Timothe Litt wrote:
On 18-Dec-17 01:07, Dave Warren wrote:
On 2017-12-15 06:23, Petr Menšík wrote:
Dne 15.12.2017 v 13:06 G.W. Haywood via bind-users napsal(a):
Hi there,
On Fri, 15 Dec 2017, Petr Men??k wrote:
... current time is not available or can be inaccurate.
On 18/12/2017 14:44, Timothe Litt wrote:
>
> On 18-Dec-17 01:07, Dave Warren wrote:
>> On 2017-12-15 06:23, Petr Menšík wrote:
>>>
>>> Dne 15.12.2017 v 13:06 G.W. Haywood via bind-users napsal(a):
Hi there,
On Fri, 15 Dec 2017, Petr Men??k wrote:
> ... current time is not
On 18-Dec-17 01:07, Dave Warren wrote:
> On 2017-12-15 06:23, Petr Menšík wrote:
>>
>> Dne 15.12.2017 v 13:06 G.W. Haywood via bind-users napsal(a):
>>> Hi there,
>>>
>>> On Fri, 15 Dec 2017, Petr Men??k wrote:
>>>
... current time is not available or can be inaccurate.
>>>
>>> ntpdate?
>>>
>
On 2017-12-15 06:23, Petr Menšík wrote:
Dne 15.12.2017 v 13:06 G.W. Haywood via bind-users napsal(a):
Hi there,
On Fri, 15 Dec 2017, Petr Men??k wrote:
... current time is not available or can be inaccurate.
ntpdate?
Sure, of course. What would be default host after installation, that ca
Hi there,
On Fri, 15 Dec 2017, Barry Margolin wrote:
In article ,
"G.W. Haywood" wrote:
On Fri, 15 Dec 2017, Petr Men??k wrote:
... current time is not available or can be inaccurate.
ntpdate?
I think the issue is that he needs to resolve the hostname of the NTP
server.
Perhaps he c
On 12/15/2017 08:10 AM, Timothe Litt wrote:
I use an 19xLVC too (On Raspbian == Debian). But I also have an RTC.
GPS does have outages, can take a while to get a fix, and NTP wants
consensus. So I use my GPS receiver as a local clock source
(preferred), but also configure several servers fr
In article ,
"G.W. Haywood" wrote:
> Hi there,
>
> On Fri, 15 Dec 2017, Petr Men??k wrote:
>
> > ... current time is not available or can be inaccurate.
>
> ntpdate?
I think the issue is that he needs to resolve the hostname of the NTP
server.
--
Barry Margolin
Arlington, MA
_
On 15-Dec-17 07:44, Mukund Sivaraman wrote:
On Fri, Dec 15, 2017 at 12:45:11PM +0100, Petr Menšík wrote:
>> Hi folks.
>>
>> I am looking for a way to validate name also on systems, where current
>> time is not available or can be inaccurate.
> I use a Garmin 18x LVC 1pps GPS receiver device conne
On 15-Dec-17 06:45, Petr Menšík wrote:
> Hi folks.
>
> I am looking for a way to validate name also on systems, where current
> time is not available or can be inaccurate.
>
> This is related to booting with NTP client, when the only configuration
> is hostname that has to be resolved. There is a
Dne 15.12.2017 v 13:06 G.W. Haywood via bind-users napsal(a):
> Hi there,
>
> On Fri, 15 Dec 2017, Petr Men??k wrote:
>
>> ... current time is not available or can be inaccurate.
>
> ntpdate?
>
Sure, of course. What would be default host after installation, that can
be used in default install
Petr Menšík wrote:
>
> This is related to booting with NTP client, when the only configuration
> is hostname that has to be resolved. There is a bit circle dependencies.
Yes awkward, and there still aren't any convincing answers. One of the
more interesting projects is https://roughtime.googlesou
On Fri, Dec 15, 2017 at 12:45:11PM +0100, Petr Menšík wrote:
> Hi folks.
>
> I am looking for a way to validate name also on systems, where current
> time is not available or can be inaccurate.
I use a Garmin 18x LVC 1pps GPS receiver device connected to RS-232
serial port. The device plus cables
Hi there,
On Fri, 15 Dec 2017, Petr Men??k wrote:
... current time is not available or can be inaccurate.
ntpdate?
--
73,
Ged.
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing li
13 matches
Mail list logo
