| View previous topic :: View next topic |
| Author |
Message |
Dizzutch
Guru
Joined: 09 Nov 2004
Posts: 463
Location: Worcester, MA
|
 Posted: Tue Sep 19, 2006 12:35 am Post subject: |
 |
|
could you add a xfer-in logging category to both the slave and the master, and repost logs?
Thanks!
-Dizz
_________________
Help the confused! Adopt an unanswered post!
prepend [solved] to your post title when you feel your issue is resolved.
Worcester Judo |
|
| Back to top |
|
 |
NiceGuy
Guru
Joined: 12 Jun 2006
Posts: 451
Location: Canada
|
| Posted: Tue Sep 19, 2006 8:03 pm Post subject: |
|
|
Hey Dizzhutch,
I added the ...
| Code: |
category xfer-in {itsa_default; };
|
to both my Master and Slave config files ..... and speaking of which both are pasted below ... I clean up previous log output .. you now only see the relevant output related to my previous adjustments.
********************
Master
*******************
| Code: |
19-Sep-2006 15:50:47.632 xfer-out: info: client 172.1.1.1#4777: transfer of '1.172.in-addr.arpa/IN': AXFR ended
19-Sep-2006 15:50:47.631 xfer-out: info: client 172.1.1.1#4777: transfer of '1.172.in-addr.arpa/IN': AXFR started
19-Sep-2006 15:50:47.607 xfer-out: info: client 172.1.1.1#4056: transfer of 'itsadomain.org/IN': AXFR ended
19-Sep-2006 15:50:47.606 xfer-out: info: client 172.1.1.1#4056: transfer of 'itsadomain.org/IN': AXFR started
19-Sep-2006 15:50:47.498 notify: info: zone itsadomain.org/IN: sending notifies (serial 2006091337)
19-Sep-2006 15:50:47.494 update: info: client 172.1.1.1#1035: updating zone 'itsadomain.org/IN': adding an RR at 'itsadomain.org' NS
19-Sep-2006 15:50:47.485 update: info: client 172.1.1.1#1035: updating zone '1.172.in-addr.arpa/IN': adding an RR at '100.100.1.172.in-addr.arpa' PTR
19-Sep-2006 15:50:47.480 notify: info: zone itsadomain.org/IN: sending notifies (serial 2006091336)
19-Sep-2006 15:50:47.458 update: info: client 172.1.1.1#1035: updating zone 'itsadomain.org/IN': adding an RR at 'Another.itsadomain.org' A
19-Sep-2006 15:50:47.043 xfer-out: info: client 172.1.1.1#2528: transfer of '1.172.in-addr.arpa/IN': AXFR ended
19-Sep-2006 15:50:47.042 xfer-out: info: client 172.1.1.1#2528: transfer of '1.172.in-addr.arpa/IN': AXFR started
19-Sep-2006 15:50:47.018 xfer-out: info: client 172.1.1.1#4859: transfer of 'itsadomain.org/IN': AXFR ended
19-Sep-2006 15:50:47.017 xfer-out: info: client 172.1.1.1#4859: transfer of 'itsadomain.org/IN': AXFR started
19-Sep-2006 15:50:08.226 xfer-out: info: client 172.1.1.1#2832: transfer of '1.172.in-addr.arpa/IN': AXFR ended
19-Sep-2006 15:50:08.225 xfer-out: info: client 172.1.1.1#2832: transfer of '1.172.in-addr.arpa/IN': AXFR started
19-Sep-2006 15:50:08.202 xfer-out: info: client 172.1.1.1#1806: transfer of 'itsadomain.org/IN': AXFR ended
19-Sep-2006 15:50:08.201 xfer-out: info: client 172.1.1.1#1806: transfer of 'itsadomain.org/IN': AXFR started
19-Sep-2006 15:50:08.091 xfer-out: info: client 172.1.1.1#1674: transfer of '1.172.in-addr.arpa/IN': AXFR ended
19-Sep-2006 15:50:08.090 xfer-out: info: client 172.1.1.1#1674: transfer of '1.172.in-addr.arpa/IN': AXFR started
19-Sep-2006 15:50:08.066 xfer-out: info: client 172.1.1.1#1090: transfer of 'itsadomain.org/IN': AXFR ended
19-Sep-2006 15:50:08.065 xfer-out: info: client 172.1.1.1#1090: transfer of 'itsadomain.org/IN': AXFR started
19-Sep-2006 15:49:36.625 notify: info: zone itsadomain.org/IN: sending notifies (serial 2006091335)
19-Sep-2006 15:49:36.625 general: notice: running
19-Sep-2006 15:49:36.623 general: info: zone itsadomain.org/IN: loaded serial 2006091335
19-Sep-2006 15:49:36.613 general: info: zone localhost/IN: loaded serial 2005010100
19-Sep-2006 15:49:36.589 general: info: zone 1.172.in-addr.arpa/IN: loaded serial 2006091317
19-Sep-2006 15:49:36.571 general: info: zone 0.0.127.in-addr.arpa/IN: loaded serial 2005010100
|
********************
Slave
********************
| Code: |
19-Sep-2006 15:50:24.587 notify: info: zone itsadomain.org/IN: sending notifies (serial 2006091335)
19-Sep-2006 15:50:24.586 general: notice: running
19-Sep-2006 15:50:24.585 general: info: zone itsadomain.org/IN: loaded serial 2006091335
19-Sep-2006 15:50:24.582 general: info: zone localhost/IN: loaded serial 2005010100
19-Sep-2006 15:50:24.578 general: info: zone 1.172.in-addr.arpa/IN: loaded serial 2006091317
19-Sep-2006 15:50:24.573 general: info: zone 0.0.127.in-addr.arpa/IN: loaded serial 2005010100
|
____________________________________________________________________________________________
I should also mention that ... my Slave seems ... though I am not certain .. to get updates only if I shut down both the Master and Slave systems .. but then again .. that still goes against the abiltiy of having the Master notify the Slave that a zone update has been preformed, and for the Slave to update itsa zone file accordingly.
Still no "notifying" going on
Thanks for yourt time
p.s -> you can see on the Master where I add a new host at:
19-Sep-2006 15:50:47.480 notify: info: zone itsadomain.org/IN: sending notifies (serial 2006091336)
19-Sep-2006 15:50:47.458 update: info: client 172.1.1.1#1035: updating zone 'itsadomain.org/IN': adding an RR at 'Another.itsadomain.org' A
but no corresonding update on the Slave side/ |
|
| Back to top |
|
|
Dizzutch
Guru
Joined: 09 Nov 2004
Posts: 463
Location: Worcester, MA
|
| Posted: Tue Sep 19, 2006 8:24 pm Post subject: |
|
|
the servers are in synch when they are loaded up, since they are both at 2006091335.
how long did you wait after adding the host, before posting the logs?
maybe add a | Code: | | allow-notify{ 172.1.1.1; }; |
to your slave
_________________
Help the confused! Adopt an unanswered post!
prepend [solved] to your post title when you feel your issue is resolved.
Worcester Judo |
|
| Back to top |
|
|
NiceGuy
Guru
Joined: 12 Jun 2006
Posts: 451
Location: Canada
|
| Posted: Thu Sep 21, 2006 7:52 pm Post subject: |
|
|
Hey again,
I added the "allow-notify { 172.1.1.1; }; " clasue to the slave .... and let the Master and Slave rum for about a day. Here is the out put of both logs.
********************
Master
********************
| Code: |
21-Sep-2006 11:58:06.498 xfer-out: info: client 172.1.5.5#1951: transfer of 'itsadomain.org/IN': IXFR ended
21-Sep-2006 11:58:06.497 xfer-out: info: client 172.1.5.5#1951: transfer of 'itsadomain.org/IN': IXFR started
21-Sep-2006 11:35:43.438 xfer-out: info: client 172.1.5.5#4668: transfer of '1.172.in-addr.arpa/IN': IXFR ended
21-Sep-2006 11:35:43.437 xfer-out: info: client 172.1.5.5#4668: transfer of '1.172.in-addr.arpa/IN': IXFR started
21-Sep-2006 09:25:54.271 xfer-out: info: client 172.1.1.1#4544: transfer of '1.172.in-addr.arpa/IN': AXFR ended
21-Sep-2006 09:25:54.270 xfer-out: info: client 172.1.1.1#4544: transfer of '1.172.in-addr.arpa/IN': AXFR started
21-Sep-2006 09:25:54.246 xfer-out: info: client 172.1.1.1#2826: transfer of 'itsadomain.org/IN': AXFR ended
21-Sep-2006 09:25:54.245 xfer-out: info: client 172.1.1.1#2826: transfer of 'itsadomain.org/IN': AXFR started
21-Sep-2006 09:25:54.146 notify: info: zone itsadomain.org/IN: sending notifies (serial 2006092005)
21-Sep-2006 09:25:54.134 update: info: client 172.1.1.1#1356: updating zone 'itsadomain.org/IN': adding an RR at 'itsadomain.org' NS
21-Sep-2006 09:25:54.124 update: info: client 172.1.1.1#1356: updating zone '1.172.in-addr.arpa/IN': adding an RR at '68.68.1.172.in-addr.arpa' PTR
21-Sep-2006 09:25:54.049 update: info: client 172.1.1.1#1356: updating zone 'itsadomain.org/IN': adding an RR at 'morning.itsadomain.org' A
|
************************
Slave
***********************
| Code: |
21-Sep-2006 12:02:21.418 notify: info: zone itsadomain.org/IN: sending notifies (serial 2006092005)
21-Sep-2006 12:02:21.417 xfer-in: info: transfer of 'itsadomain.org/IN' from 172.1.1.1#53: end of transfer
21-Sep-2006 12:02:21.417 general: info: zone itsadomain.org/IN: transferred serial 2006092005
21-Sep-2006 12:02:21.409 xfer-in: info: transfer of 'itsadomain.org/IN' from 172.1.1.1#53: connected using 172.1.5.5#1951
21-Sep-2006 12:02:21.408 general: info: zone itsadomain.org/IN: Transfer started.
21-Sep-2006 11:39:58.351 xfer-in: info: transfer of '1.172.in-addr.arpa/IN' from 172.1.1.1#53: end of transfer
21-Sep-2006 11:39:58.351 general: info: zone 1.172.in-addr.arpa/IN: transferred serial 2006092003
21-Sep-2006 11:39:58.338 xfer-in: info: transfer of '1.172.in-addr.arpa/IN' from 172.1.1.1#53: connected using 172.1.5.5#4668
21-Sep-2006 11:39:58.336 general: info: zone 1.172.in-addr.arpa/IN: Transfer started.
21-Sep-2006 00:10:09.321 notify: info: zone itsadomain.org/IN: sending notifies (serial 2006092003)
|
_________________________________________________________________________________
At around 9:25 am on the Master, I added a new host called "morning.itsadomain.org":
21-Sep-2006 09:25:54.049 update: info: client 172.1.1.1#1356: updating zone 'itsadomain.org/IN': adding an RR at 'morning.itsadomain.org' A
The notify from the Master was sent a few seconds later at:
21-Sep-2006 09:25:54.146 notify: info: zone itsadomain.org/IN: sending notifies (serial 2006092005)
The slave did not recieve a notify until :
21-Sep-2006 12:02:21.418 notify: info: zone itsadomain.org/IN: sending notifies (serial 2006092005)
Though to be honest, I am assuming that is what this line is saying, true??
So that's approximately a difference of 2.5 hours ... does that sound about right?? Something tells me you'll probably answer no ... but I just though I should ask.
Thanks again |
|
| Back to top |
|
|
Dizzutch
Guru
Joined: 09 Nov 2004
Posts: 463
Location: Worcester, MA
|
| Posted: Tue Sep 26, 2006 6:50 pm Post subject: |
|
|
hmm, it's not normal, and the notify yes statements should make the notify go through right away.
not sure what's going on. times synched up?
_________________
Help the confused! Adopt an unanswered post!
prepend [solved] to your post title when you feel your issue is resolved.
Worcester Judo |
|
| Back to top |
|
|
|
Networking & Security
