Log entries explanation

User, Public public at seajay.com
Tue Jan 6 05:14:12 UTC 2004


Are you sure that the zone files on 66.164.47.3 are getting the serial
number updated?  It looks like the primary has notified the secondary
(that log) that there is an update, but the serial number is not
incrementing or is not different than what the secondary already has.
When making changes to the primary zone files on the primary server,
make sure the serial number is updated for that zone.

If you have already done this, I am not sure what the log entries are
for.  Mistyped IP address?  Missing NS record?

Chris


Christopher P. Jenkins, Senior Consultant

Concordant, Inc.

P:  508-820-3080

F:  508-820-4367

C:  508-241-7415

E:  chris.jenkins at concordantinc.com


-----Original Message-----
From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org] On
Behalf Of Jim McAtee
Sent: Monday, January 05, 2004 5:44 PM
To: bind-users at isc.org
Subject: Log entries explanation

Can anyone explain the following log entries to me.  What does the
"nonincremental response" entry imply?  Does it have something to do
with the
serial number?  Why does the third entry mention the old serial, since
the
new serial on Dec 4 would have been 2003120401?


Dec  4 15:21:06.384 notify: info: received notify for zone 'xyz.com'

Dec  4 15:21:06.525 xfer-in: debug 3: transfer of 'xyz.com/IN' from
66.164.47.3#53: connected

Dec  4 15:21:06.525 xfer-in: debug 3: transfer of 'xyz.com/IN' from
66.164.47.3#53: requesting IXFR for serial 2003101701

Dec  4 15:21:06.525 xfer-in: debug 3: transfer of 'xyz.com/IN' from
66.164.47.3#53: sent request length prefix

Dec  4 15:21:06.525 xfer-in: debug 3: transfer of 'xyz.com/IN' from
66.164.47.3#53: sent request data

Dec  4 15:21:06.743 xfer-in: debug 3: transfer of 'xyz.com/IN' from
66.164.47.3#53: got nonincremental response

Dec  4 15:21:06.821 xfer-in: info: transfer of 'xyz.com/IN' from
66.164.47.3#53: end of transfer




More information about the bind-users mailing list