Return to BSD News archive
Newsgroups: comp.unix.bsd.bsdi.misc Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.cs.su.oz.au!metro!metro!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!cpk-news-hub1.bbnplanet.com!news.bbnplanet.com!news-peer.sprintlink.net!news.sprintlink.net!sprint!ix.netcom.com!jpdavid From: jpdavid@netcom.com (hockey fan) Subject: dns failure - Time Warp Message-ID: <jpdavidE8uxx6.n39@netcom.com> Organization: Alcoholics Anomalous Date: Fri, 18 Apr 1997 23:43:53 GMT Lines: 31 Sender: jpdavid@netcom22.netcom.com Xref: euryale.cc.adfa.oz.au comp.unix.bsd.bsdi.misc:6672 I am running a BSDI 2.1 box as a secondary name server. I noticed that over the last year or so, the time on the primary had slipped forward about 10 hours, and the time on the secondary (BSDI) has slipped forward about 4 hours. First on the primary, I set the time, then I went over and set the time on secondary name server. About an hour later, I noticed that name lookups using the secondary server were failing. I went to the console, and couldn't lookup anything, including itself. I looked at the db records, and everything seemed good. I figured named must have just broken. I ran named.restart, and got the error: db.dname Time Warp I figured the problem must be related to changing the time backwards. So I set it forward 1 day, and now it is working again. Question: How can I set the correct time without freaking named out? Was it the fact that I set the primary time back, secondary time back, or both? Any explanation of how time affects dns would be appreciated! Thanks! jk -- | John Kordic | jpdavid@netcom.com | // Amiga!! :( :( | | Fight On USC! | Go Kings! Go Ducks! | \X/ 'O Bar E O Meu Lar!' |