[juneau-lug] Re: named is in a time warp...
- From: Stephen <sbodnar@xxxxxxx>
- To: juneau-lug@xxxxxxxxxxxxx
- Date: Tue, 02 Mar 2004 18:39:15 -0900
>Here's an interesting one. The server I recently upgraded to FC2 is
>also my ddns/dhcp server.
>
>Here's a sample log entry:
>
>Mar 2 18:01:42 Lightyear dhcpd: Added new forward map from
>Juneau-LUG.sodorline.home to 192.168.1.128
>Mar 2 22:01:42 Lightyear named[2691]: client 192.168.0.42#32782:
>updating zone '1.168.192.in-addr.arpa/IN': deleting an rrset
>Mar 2 22:01:42 Lightyear named[2691]: client 192.168.0.42#32782:
>updating zone '1.168.192.in-addr.arpa/IN': adding an RR
>Mar 2 18:01:42 Lightyear dhcpd: added reverse map from
>128.1.168.192.in-addr.arpa. to Juneau-LUG.sodorline.home
>
>Hmm. Named is living four hours in the future. Perhaps my system clock
>is messed up, and it thinks that time is UTC?
>
>$date
>Tue Mar 2 18:12:36 AKST 2004
>
>doesn't look good. Let's make sure:
>
>$date --utc
>Wed Mar 3 03:13:18 UTC 2004
>
>So, any ideas why named would be living on the east coast? Is it a
>Virginia thing that Fedora puts in?
>
>Cheers,
>
>James
I've had very similar things happen. The machine I just put FC1 on
was 2 hours off. What I did was set the bios clock time and date
to UTC, the timezone to Alaska, and set the timeserver in
/etc/ntp.conf to utcnist.colorado.edu, which is the National
Institute of Standards in Boulder. After a reboot and a few hours
for the clock to sync on the timeserver,it came up spot on.
Stephen
------------------------------------
This is the Juneau-LUG mailing list.
To unsubscribe, send an e-mail to juneau-lug-request@xxxxxxxxxxxxx with the
word unsubscribe in the subject header.
- References:
- [juneau-lug] named is in a time warp...
- From: James Zuelow
Other related posts:
- » [juneau-lug] named is in a time warp...
- » [juneau-lug] Re: named is in a time warp...
- » [juneau-lug] Re: named is in a time warp...
- [juneau-lug] named is in a time warp...
- From: James Zuelow