[754] in linux-net channel archive
Re: netdate setup problems
daemon@ATHENA.MIT.EDU (Chris Woods)
Sat Jul 22 04:16:01 1995
Date: Fri, 21 Jul 1995 21:03:44 -0400 (EDT)
From: Chris Woods <cjwoods@gigotech.net>
To: Stephen Davies <scldad@sdc.com.au>
cc: Geis Jerry <GeisJ@rnd3.indy.tce.com>,
"linux-net (rutgers)" <linux-net@vger.rutgers.edu>
In-Reply-To: <199507210923.SAA03996@mustang.sdc.com.au>
On Fri, 21 Jul 1995, Stephen Davies wrote:
> One of the things on my to-do-list is to revisit the netdate source to
> pin this bug down.
>
> In the mean time, if you put a FQDN as the host parameter, it should work:
> it does for me.
Actually, this fails for me too. It seems that netdate's resolver is
acting funky. I have netdate in rc.local, and a cron running it every
hour. If I ping the netdate server before running netdate, netdate comes
back fine. If I run netdate fresh, it comes back with
"time.nist.gov: unknown host"
If, however, I have the time servers in /etc/hosts, it works fine all the
time. It seems as though your assessment of a BIND fix screwing netdate
may be accurate, although I cannot pin down a certain version of BIND,
although I am running 4.9.3beta21. (Linux 1.2.10, for statistical info)
Chris Woods cjwoods@gigotech.net
GCM/CS/E d--- H++ s+:++ !g p? au-- a- w+ v++ C++ UL++++ P++>++++ L+++ 3+
E++>+++ N+ K++ W--- M-- V-- -po+ Y+ t+ !5 !j R G? tv-- b+ D+ B-
e+ u+ h---- f r+++ n---- y++++