Date: Wed, 04 Jul 2018 14:45:33 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 144804] ntpd(8) cannot resolve hostnames at system start Message-ID: <bug-144804-227-6mhvSYOCFe@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-144804-227@https.bugs.freebsd.org/bugzilla/> References: <bug-144804-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=144804 Ian Lepore <ian@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ian@FreeBSD.org Status|Open |Closed Resolution|--- |Overcome By Events --- Comment #7 from Ian Lepore <ian@FreeBSD.org> --- This should no longer be a problem with our modern ntp.conf. We've switched from specific hostnames to the 'pool' feature that adds hosts from the pool as needed. The pool management is fully dynamic, periodically adding new servers when there not enough available, which amounts to automatic retries following dns failures at startup time. When it is necessary to have ntpd set time before allowing rc processing to conclude, options to ensure ntpd can resolve names include setting the interface config to SYNCDHCP instead of plain DHCP, or add one or more interface names to the netwait_if= list in rc.conf to ensure the names will resolve at startup. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-144804-227-6mhvSYOCFe>