I've just set up a server to use Hammernode for dynamic DNS (and thanks to Paul Chubb for his posting on that subject). On reboot, I checked the messages file and noticed that the system time changed in the log when the named was processing:
Apr 15 19:26:23 mistral rc: Starting smb: succeeded
Apr 16 02:26:24 mistral named[215]: named shutting down
Apr 16 02:26:24 mistral named[1266]: starting (/etc/named.conf). named 8.2.3-REL Sat Jan 27 05:11:05 EST 2001 ^Iprospector@porky.devel.redhat.com:/usr/src/bs/BUILD/bind-8.2.3/src/bin/named
Apr 16 02:26:24 mistral named[1266]: hint zone "" (IN) loaded (serial 0)
Apr 16 02:26:24 mistral named[1266]: Zone "0.0.127.in-addr.arpa" (file named.local): No default TTL ($TTL ) set, using
SOA minimum instead
Apr 16 02:26:24 mistral named[1266]: master zone "0.0.127.in-addr.arpa" (IN) loaded (serial 1997022700)
Apr 16 02:26:24 mistral named[1266]: master zone "1.168.192.in-addr.arpa" (IN) loaded (serial 2001040600)
Apr 16 02:26:24 mistral named[1266]: master zone "domainname.ca" (IN) loaded (serial 2001040600)
Apr 16 02:26:24 mistral named[1266]: listening on [127.0.0.1].53 (lo)
Apr 16 02:26:24 mistral named[1266]: listening on [192.168.1.1].53 (eth0)
Apr 16 02:26:24 mistral named[1266]: Forwarding source address is [0.0.0.0].1025
Apr 16 02:26:24 mistral named[1266]: chrooted to /home/dns
Apr 16 02:26:24 mistral named[1266]: group = dns
Apr 16 02:26:24 mistral named[1266]: user = dns
Apr 16 02:26:24 mistral named[1266]: Ready to answer queries.
Apr 15 19:26:46 mistral kernel: Packet log: denylog DENY eth1 PROTO=6 216.232.1.98:64422 216.232.204.115:22 L=44 S=0x10 I=9046
I'm on Pacific Daylight Time (in British Columbia, Canada), so the time is displaying +7, UDT. As can be seen, the subsequent entry is back on PDT. Can someone explain why this change would occur?
Thanks,
Des Dougan