Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!mintaka!spdcc!dirtydog.ima.isc.com!ism.isc.com!ispd-newsserver!dcox From: dcox@ssd.kodak.com (Don Cox ) Newsgroups: comp.protocols.tcp-ip.domains Subject: decimals in the serial field Message-ID: <1991Jun13.161911.29541@ssd.kodak.com> Date: 13 Jun 91 16:19:11 GMT Sender: news@ssd.kodak.com Distribution: na Organization: Eastman Kodak Lines: 40 Originator: dcox@netman.ssd.kodak.com SunOS4.1.1, Sun3/60, BIND 4.8.3 I have a primary nameserver and a secondary for ssd.kodak.com. On the primary machine I have the following entry: ssd.kodak.com. IN SOA ispdgate.ssd.kodak.com. dcox.ssd.kodak.com. ( 32.1 ; Serial ^^^^ 1800 ; Refresh every 30 minutes 300 ; Retry every 5 minutes 604800 ; Expire after one week 3600 ) ; Minimum If I look at the file for ssd.kodak.com on the secondary I get: ssd IN SOA ispdgate.ssd.kodak.com. dcox.ssd.kodak.com. ( 320001 1800 300 604800 3600 ) ^^^^^^ If I make a change on the primary, it doesn't get transfered to the secondary for up to 24 hours. Is this because the secondary is somehow translating the serial number into 320001 when it's 32.1 on the primary? Wouldn't this mean that the secondary would never get updated, since 32.1 would never be greater than 320001? When I changed the serial number on the primary to 320002 (so that it would be greater than the number on the secondary) the transfers started taking place every 30 minutes, as specified in the refresh. When I looked at the access time for ssd.kodak.com on the secondary (ls -la) it changed every three hours whether I incremented the serial number on the primary or not. Is this just because the file was 'touched' to verify the serial number on the secondary, and there wasn't an actual transfer from primary to secondary? Thanks much. -- Don Cox Phone (716) 253-7121 KMX (716) 253-7998 INTERNET dcox@ssd.kodak.com