On 09/01/2015 10:28 AM, John Miller wrote:
On Tue, Sep 1, 2015 at 9:31 AM, Robert Moskowitz <r...@htt-consult.com> wrote:
On 09/01/2015 09:20 AM, John Miller wrote:
If you check pcap, logs, etc., is the server's following delegation
for 0.centos.pool.ntp.org? Where do outbound packets stop?
I don't believe this and I have some serious problems.
Part of my challenge is I am running the new server on an armv7 board that
does not have a rtc. So when the system boots, the time is jan 1 1970. The
first thing you want to run is ntp to set the time, but requires named
running and resolving.
For the 'fun' of it, I used 'date' to set the time to now, and then no
problem resolving 0.centos.pool.ntp.org. So there is something about that
resolution that does not like the early date.
So I am caught in a time bind here!
Is there anyway to get bind not to be particular about system time at first?
Hopefully this isn't a production server... rtc's kind of important
;-)
Lack of a battery for the system clock is the norm for arm boards. They
pretty much expect network time. This is a problem with designing a
mobile arm solution.
I'll ditto here and say: static /etc/hosts entries or static IPs in ntp.conf.
Definitely the obvious punt.
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
