Fwd: ntpd couldn't resolve host name on system boot

Scott, Brian brian.scott4 at det.nsw.edu.au
Sat May 19 08:33:03 UTC 2012


> 
> Matthew,
> 
> Although netwait will probably fix the problem for you, another
> possibility that I have just ran into recently involved DNSSEC
> validation in bind. The problem was that without ntp syncing the time at
> boot (the system doesn't have battery backed time) dns resolution failed
> (root key wasn't valid yet). If dns resolution fails then you can't find
> your time servers. Repeat till you get sick of it.
> 
> Possible solutions include:
> *    Don't do dnssec validation
> *    Hard code an IP address in your ntp.conf (even a low stratum
> server somewhere)
> *    Run a task at startup to brute force your time to something
> reasonable (within a year or two ago) to allow dnssec validation to
> work.
> 
> As I said, you will probably find that netwait_* is all you need and you
> can safely ignore this.
> 
> Brian
> 
> -----Original Message-----
> From: owner-freebsd-stable at freebsd.org
> [mailto:owner-freebsd-stable at freebsd.org] On Behalf Of Matthew Doughty
> Sent: Friday, 18 May 2012 1:03 AM
> To: freebsd-stable at freebsd.org
> Subject: ntpd couldn't resolve host name on system boot
> 
> Dear Jerermy,
> 
> Whilst searching for a solution to a problem, I found your post:
> http://lists.freebsd.org/pipermail/freebsd-stable/2011-October/064350.ht
> ml
> 
> Please could you explain how I can implement the netwait script to solve
> the problem?  I'm new to freenas/BSD but am willing to try working from
> the Cmd line.
> 
> Best regards,
> 
> Matthew
> 
> 
> PS: Here are the messages
> 
> May 14 13:32:59 freenas kernel: SMP: AP CPU #1 Launched!
> 
> May 14 13:32:59 freenas kernel: GEOM: da0s1: geometry does not match
> label (16h,63s != 255h,63s).
> 
> May 14 13:32:59 freenas kernel: GEOM: da0s2: geometry does not match
> label (16h,63s != 255h,63s).
> 
> May 14 13:32:59 freenas kernel: Trying to mount root from
> ufs:/dev/ufs/FreeNASs2a
> 
> May 14 13:32:59 freenas kernel: WARNING: /data was not properly
> dismounted
> 
> May 14 13:32:59 freenas kernel: ZFS filesystem version 4
> 
> May 14 13:32:59 freenas kernel: ZFS storage pool version 15
> 
> May 14 13:33:00 freenas ntpd[1512]: ntpd 4.2.4p5-a (1)
> 
> May 14 13:33:00 freenas root: /etc/rc: WARNING: failed precmd routine
> for vmware_guestd
> 
> May 14 13:33:02 freenas ntpd_initres[1526]: host name not found:
> 0.freebsd.pool.ntp.org
> 
> May 14 13:33:02 freenas ntpd_initres[1526]: couldn't resolve `
> 0.freebsd.pool.ntp.org', giving up on it
> 
> May 14 13:33:02 freenas ntpd_initres[1526]: host name not found:
> 1.freebsd.pool.ntp.org
> 
> May 14 13:33:02 freenas ntpd_initres[1526]: couldn't resolve `
> 1.freebsd.pool.ntp.org', giving up on it
> 
> May 14 13:33:02 freenas ntpd_initres[1526]: host name not found:
> 2.freebsd.pool.ntp.org
> 
> May 14 13:33:02 freenas ntpd_initres[1526]: couldn't resolve `
> 2.freebsd.pool.ntp.org', giving up on it
> _______________________________________________
> freebsd-stable at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to
> "freebsd-stable-unsubscribe at freebsd.org"

**********************************************************************
This message is intended for the addressee named and may contain
privileged information or confidential information or both. If you
are not the intended recipient please delete it and notify the sender.
**********************************************************************


More information about the freebsd-stable mailing list