> Setting date via ntp.
> Exiting, name server cannot be used: Temporary failure in name resolution
> (2)16 Jun 21:23:49 ntpdate[1082]: name server cannot be used: Temporary
> failure in name resolution (2)
> /etc/rc.d/ntpdate exited with code 1
> [...]
>
> ntp is running by the time I get to X
> Any clues?
So all's well, eventually, and you could ignore the initial problem
(the Temporary failure).
It could be worse:
- you rely on hostnames in ntp.conf, and thusly on a working
DNS resolver
- the resolver is depending on working DNSSEC, but that won't
work until the time is not too far off.
==> catch 22. Neither ntpd nor resolving will start.
In that case, setting the time manually (date(1)) will allow you
to get going.
On amd64 platforms, netbsd should initialize its clock from the
computer's battery-backed-up real-time-clock. It should be set
to the proper date & UTC(!) time in the BIOS/UEFI.
Another typical cause of such problems can be "the network interface
is not operational yet", and that can be because your switch(!) is
keeping the ethernet port in the "learning" state of the spanning
tree protocol for the first 30 seconds after link activation. (On
cisco switches, this is recognizable by an amber status light on
the port in question.) Switches worth their salt can be configured
to speed this up.
Martin
